Aws-cli: --output text results in "None" while --output json gives correct result on cloudformation changesets

[konstantinj]

Hi,

the following gives "CREATE_COMPLETE" which is correct

aws cloudformation describe-change-set --change-set-name website-production-alb-a-1-0-7 --stack-name website-production-alb-a

while this gives "None" which is incorrect

aws cloudformation describe-change-set --change-set-name website-production-alb-a-1-0-7 --stack-name website-production-alb-a --output text

aws --version
aws-cli/1.16.110 Python/3.7.2 Darwin/18.2.0 botocore/1.12.100

colleague has aws-cli/1.16.1 which also gives correct result on text.

[mivtachyahu]

I have also noticed this problem, same version, but linux.
Iterating through versions using pip --user installs, I can see that this regression was introduced in release version 1.16.108

[sriramho]

Try using --no-paginate switch to the command and see if it resolves the issue.

[konstantinj]

@sriramho
it does, thanks!

But y?!

[swetashre]

@konstantinj - Thank you for reporting the behavior. I was able to reproduce the issue and confirmed it as a bug. We are looking into getting this resolved.

Followings are the commands were used to reproduce the problem:

$ aws cloudformation describe-change-set --change-set-name mychangeset --stack-name mystack --output text

$ aws cloudformation describe-change-set --change-set-name mychangeset --stack-name mystack --output text --no-paginate

I found CLI version 1.16.100 gives correct result but returns none with version 1.16.110. If the option --no-paginate is used with version 1.16.110 it returns the correct result.