-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: Support for multiple values files in helm charts #659
Comments
@bazzuka what would you want this to look like in the Pulumi API? I believe this is already possible by reading the files off disk yourself, |
values (Optional[pulumi.Inputs]) – Optional overrides for chart values. I wrote simple python example:
|
Any update? I was able to do this with helm install test -f secrets.yaml -f config.yaml --dry-run --debug path/to/chart/ |
Still on the backlog for now. If you really need this in the meantime, you can use |
Any update on this or how others are working around this? |
@viveklak Does Helm Release support this yet? |
Yes - this has been supported in helm release as of https://github.com/pulumi/pulumi-kubernetes/releases/tag/v3.12.1 |
Brilliant! @griffithq would that be an option for you? |
Thanks @viveklak - are there any docs on how to use this? |
Here's the documentation on how to use multiple values files with the Sorry to report that |
Update: the upcoming Chart v4 resource has full support for multiple values files. Enjoy! """A Kubernetes Python Pulumi program"""
import pulumi
from pulumi_kubernetes.helm.v4 import Chart,RepositoryOptsArgs
nginx = Chart("nginx",
chart="bitnami/nginx",
value_yaml_files=[
pulumi.FileAsset("path_to_values/values.default.yaml"),
pulumi.FileAsset("path_to_values/values.release.yaml")
],
values={
"service": {
"type": "ClusterIP"
},
"notes": pulumi.FileAsset("./notes.txt")
}
) |
Add ability to include multiple files to
helm template
command, like --values values1.yaml --values values2.yaml directly from filesystem.From helm documentation:
Thanks in advance
The text was updated successfully, but these errors were encountered: