'=' in env value is invalid
Closed this issue · 1 comments
christophpe commented
Describe the bug
We defined a Jenkins Secret that contains a URL with an API key including the equals sign '='. This secret is defined in a Jenkinsfile and we wanted to then reference it in notifications.yaml.
Unfortunately this broke the build indicating that the secret cannot be found.
How to reproduce
Steps to reproduce the behavior:
- create a Jenkins secret that contains '='
- reference secret in Jenkinsfile
- reference env var from Jenkinsfile in a yaml file like "{{ .Env.ENV_VAR_CONTAINING_URL }}"
Expected behavior
The secret (URL) being picked up correctly as an env value.
Additional context
Related internal slack thread
AhmedEJ commented
I can confirm the same issue is present when using a Jenkins stringParam text parameter that gets populated with a string that contains the = sign.