Backslashes in Vsphere passwords are interpreted as escape characters in generated YAML #7623
Labels
external
An issue, bug or feature request filed from outside the AWS org
kind/enhancement
New feature or request
What happened:
EKS Anywhere installation on vSphere failed with error:
"error: error parsing STDIN: error converting YAML to JSON: yaml: line 11: found unexpected end of stream\n"}
I found that in the generated YAML config, the vSphere password is being added as a value in between double quotes. When the backslash is at the end, it escapes the last double quote. I presume that when the backslash is not at the end, the password is just incorrect when converted to JSON.
What you expected to happen:
Expected the EKS Anywhere installer to begin creating cluster nodes in vSphere.
How to reproduce it (as minimally and precisely as possible):
Use a vSphere password with a backslash, exported to the shell with:
export EKSA_VSPHERE_PASSWOR='mypassword\'
Anything else we need to know?:
Environment:
The text was updated successfully, but these errors were encountered: