Open rahul-ve opened 1 year ago
Same for me, it's problematic to parse it for example with jq program. And what if the value will contain comma, then it will be:
{pets:dog,cat,owner:tom}
instead:
{"pets":"dog,cat","owner":"tom"}
Curly bracket inside value will break everything as well.
Hopefully this bug is fixed soon, as there is no way to get the exact value from a Secrets stored as a JSON, In my case I had to use awk
and sed
to extract the value, for OP's case would be like:
build-var-my-secret=$(echo $(build-var-my-secret) | awk -F ':' '{print $2}' | sed 's/}//')
echo $build-var-my-secret #will print bar
Describe the bug
Not sure if I am doing something wrong or a bug! I am using Secrets Manager Get secret task and saving the secret value to a variable. When I print the variable, I was expecting it to be valid JSON but it is not.
To reproduce
Expected behavior
was expecting valid JSON
{"foo":"bar"}
Instead got
{foo:bar}
Screenshots
Your Environment
Thanks!