-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CloudFormation CLI parameters parsing issue #2392
Comments
I've also tried passing it as a
|
Have you tried something like this?
The single quotes ensure to use the literal value and the double quotes should ensure that spaces are not interpreted as additional values in |
I get the same issue:
|
Is there a character limit to how long the parameters can be? |
FWIW, I'm using Jenkins as an interface to deploy my CloudFormation template. I don't want to check in my GitHub Deploy Key into a |
There is no limit on the value you can provide to the CLI command. So it may be a limit in the Jenkins interface. What OS are you running this on? Also could you run the command with |
Hm. I'll try the debug flag. I'm getting the same issue if I run the command locally, so it seems unlikely that it's a limitation with my Jenkins interface. |
Ah, Doing |
I'm unable to pass an
ssh
key in as a comma-delimitted-string and get parsing errors. I've iterated through a couple of times and get slightly different parsing errors, below is a list of the command run and the error I get:Next I tried to wrap the Parameter with
"
. Note that it added single quotes inside the parameter value (afterBEGIN
and beforeKEY
)I also tried to surround the ParameterKey=..,ParameterValue.. block in single quotes
'
, with the actual RSA key surrounded with double quotes"
. Again, note the added'
s afterBEGIN
and beforeKEY
.I have also tried escaping the
,
s with a\
to no avail. How do I pass a key as comma separated with spaces using the CLI tool?The text was updated successfully, but these errors were encountered: