APE-8064 - Support one or more values.yaml file as an input to helm scan #1501
Conversation
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
…ascan into bugfix/helm-values
|
Kudos, SonarCloud Quality Gate passed!
|
Rchanger
approved these changes
Jan 19, 2023
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.
Some of the customers are not using default values.yaml file, they have different values.yaml with different name.
As a feature helm supports multiple values.yaml files. They get merged together where right most file gets precedence for variables.
Code is added to accept comma separated values files in
terrascan scan --values-files=file1.yaml,file2.yamlThese files if more than 1 are deep merged and then given for further processing.