feat(cloudformation-stack): add ForceDeleteStack setting - #2
Merged
Conversation
CloudFormation's DeleteStack API supports DeletionMode=FORCE_DELETE_STACK, which drops the stack record even when individual resources fail to delete. The stack's orphaned resources remain in the account, but the stack itself is gone and won't keep retrying. Useful for tear-down scenarios (e.g. sandbox cleanup) where the goal is to release the stack rather than preserve its resources, and where any orphans will be cleaned up by subsequent passes. Opt-in via the new Settings flag; default behavior is unchanged.
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
1 participant
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.
Fork-side review for the upstream PR ekristen#985.
Adds a new opt-in
ForceDeleteStacksetting that passesDeletionMode=FORCE_DELETE_STACKtoDeleteStack. CloudFormation drops the stack record even when resources fail to delete, leaving orphans rather than the stack stuck in DELETE_FAILED.Useful for tear-down scenarios where the goal is to release the stack, not preserve its resources — sandbox/CI account cleanup is the common case.
Default behavior is unchanged. Existing
CreateRoleToDeleteStackandUseCurrentRoleToDeleteStackflows are untouched.