Aws-cli: Wrong Exit Status with Cloudformation on "No changes to deploy"

[sourceindex]

Hi,

as mentioned in the following ticket the wrong return code of awscli breaks our buildpipeline and makes automation impossible.

https://github.com/awslabs/serverless-application-model/issues/71

Command

aws cloudformation deploy XXX

Output

Waiting for changeset to be created..
No changes to deploy. XXX is up to date

Return Code

Exit Status:  255 ELIFECYCLE

System Info

Version Details

aws --version
aws-cli/1.15.26 Python/2.7.13 Linux/4.14.33-51.37.amzn1.x86_64 botocore/1.10.26

System Details

Debian GNU/Linux 9.4 (stretch) Release:       9.4 Codename:   stretch
Linux f2f521fcf707 4.14.33-51.37.amzn1.x86_64 #1 SMP Thu May 3 20:07:43 UTC 2018 x86_64 GNU/Linux

[kyleknap]

Hmm. Looks like this PR got merged that provides a workaround: https://github.com/aws/aws-cli/pull/2922. There is more context there, but to start returning a return code of 0 would be backwards incompatible. So we introduced a --no-fail-on-empty-changeset flag that you can set to have a return code of 0 be set for these scenarios. We cannot really change the default till a new major version of the CLI. Let us know if you have anymore follow up questions.

[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.