-
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
values from "environments" section are not reachable #957
Comments
@dududko Hey! I believe this is due to how Double Rendering works. I'm working hard to deprecate it and make a more intuitive alternative as the default in #932, but in the meantime, try moving
|
This also appears to be an issue if you reference base: environments.yaml at the top, I have to manually merge them into the main helmfile to get the values to propagate correctly. |
Note: I keep getting questions like this for 2 years. The short answer is to use
|
Also see #2036 (comment) |
Problem
When I pass the object to environment values the
helmfile.yaml
templating fails.Here is the example.
helmfile build output:
However it works if I pass the value with a flag
--state-values-set=namespace.name=test
, or when there is no nesting in valuesObservation
The content of
{{ .Values }}
is actually correct:map[namespace:map[name:hello-world]]
, also I can access thenamespace
field with{{ .Values.namespace }}
, but all dict operation on this object fail.The text was updated successfully, but these errors were encountered: