Aws-cli: Whitespaces not handled properly in cloudformation deploy parameter overrides

[saiviswanath]

[saiviswanath]

aws-cli/1.16.140 Python/2.7.12 Linux/3.10.0-957.10.1.el7.x86_64 botocore/1.12.130

Currently when running aws cloudformation deploy \
--template-file <> \
--stack-name <> \
--capabilities CAPABILITY_NAMED_IAM \
--no-fail-on-empty-changeset \
--parameter-overrides <> \
--tags <>

whitespaces are not properly handled in --parameter-overrides.

Eg: --parameter-overrides Foo=A B C Foo1=Foo2
characters post whitespace are ignored. It takes it as Foo=A.

Tried
--parameter-overrides Foo="A B C" Foo1=Foo2
--parameter-overrides "Foo=A B C" Foo1=Foo2
--parameter-overrides Foo="A\ B\ C" Foo1=Foo2

[swetashre]

@saiviswanath - Thank you for your post .It looks like that CLI is taking A,B and C as three different value because of the space .That's why its taking Foo=A and in this case it will give an error.
It should work by quoting the entire "Key=Value". It looks like this is a duplicate of #3274.
Let me know if it works for you .

[no-response[bot]]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

[saiviswanath]

@swetashre- Quoting the entire key value like "Key=Value" even doesn;t work. As shown in my examples as well.

[Fectorez]

Try this :
--parameter-overrides "key=my\ value"
Works on PowerShell

[kdaily]

@saiviswanath does this fix this for you?

[github-actions[bot]]

Greetings! It looks like this issue hasn’t been active in longer than a week. We encourage you to check if this is still an issue in the latest release. Because it has been longer than a week since the last update on this, and in the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or add an upvote to prevent automatic closure, or if the issue is already closed, please feel free to open a new one.