-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
CFNV2: defer deletions for correcting deploy order #12936
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Test Results (amd64) - Integration, Bootstrap 5 files 5 suites 2h 21m 36s ⏱️ Results for commit 87d33ca. ♻️ This comment has been updated with latest results. |
@simonrw we should convert this PR to a draft for now |
6666cde
to
bb135e7
Compare
bb135e7
to
21bf39b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for implementing this 👍
# perform all deferred actions such as deletions. These must happen in reverse from their | ||
# defined order so that resource dependencies are honoured | ||
# TODO: errors will stop all rollbacks; get parity on this behaviour | ||
for action in self._deferred_actions[::-1]: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggestion: Consider setting the stack status to UPDATE_COMPLETE_CLEANUP_IN_PROGRESS
when the deferred actions are being executed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's a great idea, thanks @pinzon !
d87da8e
to
87d33ca
Compare
Motivation
CloudFormation ensures that resources that require replacement are deleted once the new stack state is fully deployed. It also removes resources in reverse order of their dependency chain.
Changes