Due to the current string splitting logic, the spaces before the env variables become a part of the variable passed to Rancher (1.6.30) which result in an invalid env variable which appears in the Rancher UI (e.g. <space>DB_HOST, incl. the space) but is not passed to the container.
Expected outcome:
Variable names and values are trimmed when passing as string with --variables option.
Actual behaviour: When passing multiple variables alongside with the
--variables
multiline configuration might be used:Which result in the following command after YAML is processed:
Due to the current string splitting logic, the spaces before the env variables become a part of the variable passed to Rancher (1.6.30) which result in an invalid env variable which appears in the Rancher UI (e.g.
<space>DB_HOST
, incl. the space) but is not passed to the container.Expected outcome: Variable names and values are trimmed when passing as string with
--variables
option.