You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Helm charts often contain multiple values files (usually to override default values with per-environment values) e.g.
values.yaml
values.test.yaml
Unfortunately, currently this action only provides support for a single values file not giving any choice to the usr to override the defaults with test values or whatnot
Describe the solution you'd like
I'd like to provide a list of value files so the action does something like this helm lint -f values.yaml -f values.foo.yaml .
Describe alternatives you've considered
There is no other alternative provided by helm I'm afraid -- at least not to my knowledge
Additional context
The text was updated successfully, but these errors were encountered:
There is CHART_VALUES environment variable which indeed allows to specify only one file with values. Probably we can make it work with multiple values files eg. separating it with ;:
We just need to update entrypoint.sh and make it to parse CHART_VALUES variable. Currently I don't have time for this implementation, but you're welcome to create a pull request with this change
Is your feature request related to a problem? Please describe.
Helm charts often contain multiple values files (usually to override default values with per-environment values) e.g.
values.yaml
values.test.yaml
Unfortunately, currently this action only provides support for a single
values
file not giving any choice to the usr to override the defaults with test values or whatnotDescribe the solution you'd like
I'd like to provide a list of value files so the action does something like this
helm lint -f values.yaml -f values.foo.yaml .
Describe alternatives you've considered
There is no other alternative provided by
helm
I'm afraid -- at least not to my knowledgeAdditional context
The text was updated successfully, but these errors were encountered: