You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When using configuration in templating, if the value fetch from configstore is a raw value (such as a SSH key),
utask engine try to unmarshal it with yaml
In the case of a SSH key, the yaml.Unmarshal succeeds, but transform all \n into spaces.
The SSH key used in a utask template, given to the SSH plugin, is not usable.
Proposed fix
I guess we should add a new templating store, named configraw, and put the raw value there, without any yaml.Unmarshal.
In that way, if user want to use a raw value such as a SSH key, it can come from this store.
Describe the bug
When using configuration in templating, if the value fetch from configstore is a raw value (such as a SSH key),
utask engine try to unmarshal it with yaml
utask/engine/engine.go
Line 89 in 53a7164
In the case of a SSH key, the yaml.Unmarshal succeeds, but transform all
\n
into spaces.The SSH key used in a utask template, given to the SSH plugin, is not usable.
Proposed fix
I guess we should add a new templating store, named
configraw
, and put the raw value there, without any yaml.Unmarshal.In that way, if user want to use a raw value such as a SSH key, it can come from this store.
utask version impacted by the bug
All
cc @Alkorin
The text was updated successfully, but these errors were encountered: