Validation for the container image name #565
Merged
Merged
Conversation
69b4be6 to
cdea138
Compare
Contributor
Author
|
Performed manual test where I used below config for PodSpecPatch and got the error added through this PR
Here is the run I performed locally with the error: `just run --config values.yaml go run ./... --config values.yaml Error: failed to parse config: container image contains uppercase letters: example.org/MYIMAGE@latest 2025/04/14 12:37:10 failed to parse config: container image contains uppercase letters: example.org/MYIMAGE@latest` |
cdea138 to
5996822
Compare
This file contains hidden or 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
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.
Through this PR we are adding a validation for the container image name in podSpecPatch in the config provided