BitBucket Cloud Pipelines
aws-cloudformation-deploy Pipe version 0.10.0
TLDR; If a stack is in UPDATE_ROLLBACK_COMPLETE state and the next pipeline running against that stack results in "No updates are to be performed for stack", the pipe fails because stack state isn't UPDATE_COMPLETE
The scenario that occurred:
It's expected that the PIPE can detect when no changes are needed and treat that as a success regardless of the CloudFormation stack. This is how the AWS stack update process works and stack state changes only occur when changes are actually made.
Status: Downloaded newer image for bitbucketpipelines/aws-cloudformation-deploy:0.10.0
INFO: Using default authentication with AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY.
INFO: Found credentials in environment variables.
INFO: Using stack template from ./deploy.yml for deploy.
INFO: Validating the template.
INFO: Updating the stack for STACKNAME_IN_UPDATE_ROLLBACK_COMPLETE.
WARNING: No updates are to be performed for stack STACKNAME_IN_UPDATE_ROLLBACK_COMPLETE.
INFO: Waiting for update COMPLETE status...
✖ Failed to update the stack. Status UPDATE_ROLLBACK_COMPLETE.
Hi, Bitbucket community! Are you a DevOps practitioner (or know one in your network)? Do you have DevOps tips, tricks, or learnings you'd like to share with the community? If so, we'd love to hea...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events