fix nil pointer exception in jsonnet logic #1435
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
When reviewing, please make sure to expand the entire file, due to Githubs unfortunate "compression" of changed lines, it appears like the logic was changed in one function, when in fact there are two distinct changes in two distinct functions |
theSuess
approved these changes
Feb 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes a nil pointer exception caused by the logic attempting to parse SecretKeyRefs even if ConfigMapKeyRefs were declared in the
dashboard.Spec.EnvFromAdditionally, fix the
envFrom: - configMapKeyRefcase in e2e tests