-
Notifications
You must be signed in to change notification settings - Fork 564
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
How to deal with different versions in different environment? #460
Comments
I used something similar so that I could override values for dev vs production environments:
https://github.com/IDR/k8s-analysis-deploy/blob/2019.01.30/helmfile.yaml#L104 What would be nice is if
At the moment this fails if the values aren't defined:
|
So jupyterhub_public_overrides is defined in an environment specific values file as a list of files? But, in your case, empty for production? Could you elaborate a bit more, sorry for being a bit slow. |
I've got two environments with separate values files in that git repo: https://github.com/IDR/k8s-analysis-deploy/blob/2019.01.30/helmfile.yaml#L237
|
Any updates? I have the same issue. |
I guess this would be more simpler with this request developped : #359 |
Would #465 resolve your issue? With #465, I believe you can write it like:
|
Can I boil this issue down to "We need a less verbose way to achieve defaulting for environment values"? In that case,
Do you think we can resolve this after either or both of them are addressed? |
`get` is now able to take one more optional argument, that is used as the default value when the value for the key does not exist. Resolves roboll#465 Fixes roboll#427 Fixes roboll#357 Ref roboll#460
`get` is now able to take one more optional argument, that is used as the default value when the value for the key does not exist. Resolves roboll#465 Fixes roboll#427 Fixes roboll#357 Ref roboll#460
Closing this as resolved because all the suggested solutions are implemented. Please feel free to reopen if necessary! |
I found it difficult dealing with different versions across different environments
I've came up with the following but I'd love to see someone come up with something simpler.
helmfile.yaml:
env/dev.yaml:
env/prod.yaml:
Please let me know what you think.
The text was updated successfully, but these errors were encountered: