Skip to content
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

bug: 0.80.0 --state-values-set not setting more than first child in nested paths #773

Closed
bitsofinfo opened this issue Jul 26, 2019 · 2 comments · Fixed by #774
Closed

bug: 0.80.0 --state-values-set not setting more than first child in nested paths #773

bitsofinfo opened this issue Jul 26, 2019 · 2 comments · Fixed by #774

Comments

@bitsofinfo
Copy link
Contributor

See: https://github.com/bitsofinfo/helmfile-statevalue-key1

Doing this:

./helmfile --log-level debug \
  --state-values-set top.middle.x='x1' \
  --state-values-set top.middle.y='y1' \
  --file helmfile.works.yaml template

then .Values.top.middle.y has no value... only .Values.top.middle.x. Both should be populated

https://github.com/bitsofinfo/helmfile-statevalue-key1

@bitsofinfo bitsofinfo changed the title bug: --state-values-set not setting more than first child in nested paths bug: 0.80.0 --state-values-set not setting more than first child in nested paths Jul 26, 2019
@mumoshu
Copy link
Collaborator

mumoshu commented Jul 27, 2019

@bitsofinfo We had an interesting bug that caused it. #774 should be the fix.

Thanks as always for your support 😄

@bitsofinfo
Copy link
Contributor Author

thanks man!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants