fix(cli): show DELETE_FAILED events as skipped during stack updates#1564
Merged
Conversation
## Summary - During a stack update, `DELETE_FAILED` events are now displayed in gray/dim with a "(provisional)" label instead of alarming red, since CloudFormation will eventually skip these and complete the update anyway. - Stack traces and error reasons are suppressed for these provisional failures, and they are excluded from the "Failed resources" recap at the end of deployment. - During stack creation, the original behavior (red, full error details, stack traces) is preserved unchanged. ## Motivation When CloudFormation updates a stack and encounters a `DELETE_FAILED` on a resource being replaced, it will retry and ultimately succeed (or the overall update will fail for a different reason). Showing these transient states in red with full stack traces gives users the false impression that their deployment has failed, when in reality it's still in progress.
Contributor
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
rix0rrr
approved these changes
May 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
DELETE_FAILEDevents are now displayed in yellow with a "(skipped)" label instead of alarming red, since CloudFormation will eventually skip these and complete the update anyway.Motivation
When CloudFormation updates a stack and encounters a
DELETE_FAILEDon a resource being replaced, it will retry and ultimately succeed (or the overall update will fail for a different reason). Showing these transient states in red with full stack traces gives users the false impression that their deployment has failed, when in reality it's still in progress.Screenshots
While deployment is in progress
After deployment completes
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license