Support multiple values.yaml files in helm_chart

[mschulman]

Often people will use multiple values.yaml files with helm to support things like multiple environments.

Think values.yaml as a base set of values but then values.dev.yaml as env specific values.

https://helm.sh/docs/chart_template_guide/values_files/ calls out the -f flag.

I think you all support this for unittests but would be great to support for charts and then pass both sets of files in for things like lint, kubeconform etc.

While in there it might make sense to support the --set option with a "values" option in the helm_chart()

thanks!

[lilatomic]

I think this works currently, the helm_deployment.sources field will be used for helm values files. By default this is all files in the directory containing the build file with the helm_deployment target ending in ".yaml" or ".yml".

We show the usecase of deploying to multiple environments in our docs. The --set option is supported with helm_deployments.values option, in our docs that's inline values.

I want to clarify that there are 2 different target types which can work together:

• the helm_chart, which is the chart itself as source code that you might want to lint or publish to a registry
• the helm_deployment, which represents the invocation to deploy a Helm chart So you'd define a helm_chart for the files that make up the chart, and the values (and values files) for installing it with Helm would go on the helm_deployment

[github-actions[bot]]

This issue has been open for over one year without activity and is not labeled as a bug. It has been labeled as stale to invite any further updates. If you can confirm whether the issue is still applicable to the latest version of Pants, appears in other contexts, or its priority has changed, please let us know. Please feel free to close this issue if it is no longer relevant.