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
helm install/upgrade does not support commas in set flag #2952
Comments
Works fine for me with
|
This is noted in the documentation under https://docs.helm.sh/using_helm/#the-format-and-limitations-of-set, so I'm closing this as resolved. Please re-open if that fix doesn't work for you. Thanks! |
Hmm, I could have sworn that I tried escaping the comma, but I just checked back to version 2.4.0 and it worked on all of them. I clearly was mistaken, my bad. |
If anyone else comes across this via Google as I did, the updated link to the docs for |
Why does helm have a problem with commas in a string?? |
The helm cli does not seem to support a value containing a comma in the set flag for install or upgrade.
It seems that the parser is trying to look for additional keys if it finds a comma in the value. I've tried several quoting or escaping strategies and all seem to have the same issue.
The workaround is to use a value file instead of the set flag, but for my use case of passing config files through to configmaps it is easier and cleaner to manage the config files separately and cat them into a set flag than to either store them in a yaml wrapper or construct that wrapper on the fly.
The text was updated successfully, but these errors were encountered: