Output of helm version
:
Client: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}
Hello!
I like Helm, but this issue does not give me rest.
According to: https://docs.helm.sh/using_helm/#the-format-and-limitations-of-set
Sometimes you need to use special characters in your --set lines. You can use a backslash to escape the characters; --set name="value1\,value2" will become:
name: "value1,value2"
I can't guarantee that some value contains or not contains the comma.
So I forced to escape each value at my CI.
Its absolutely uncomfortable.
As I understand, you don't want to break compatibility for 2.x
.
You can consider to introduce another CLI parameter.
-s
-S
--set-value
Related issues I found:
I'm re-marking this as a feature request, and re-titling it appropriately.
Or alternatively, make --set
not treat ,
in a special way when --disable-the-damn-coma
is passed. One way or another, how things are now is extremely inconvenient. Hope this can get straightened up. :)
CC @bacongobbler
closing as a duplicate of #4030 so we can keep the conversation all in one place. Thanks!
Most helpful comment
Or alternatively, make
--set
not treat,
in a special way when--disable-the-damn-coma
is passed. One way or another, how things are now is extremely inconvenient. Hope this can get straightened up. :)CC @bacongobbler