-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
CFN: Fix duplicated stack issue #13249
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
Conversation
LocalStack Community integration with Pro 2 files ± 0 2 suites ±0 36m 9s ⏱️ - 1h 25m 26s Results for commit c7d27b1. ± Comparison against base commit 69ed784. This pull request removes 4230 tests.♻️ This comment has been updated with latest results. |
Test Results (amd64) - Integration, Bootstrap 5 files 5 suites 50m 0s ⏱️ Results for commit c7d27b1. ♻️ This comment has been updated with latest results. |
Test Results - Alternative Providers584 tests 330 ✅ 26m 5s ⏱️ Results for commit c7d27b1. ♻️ This comment has been updated with latest results. |
6ff9e82 to
675a662
Compare
simonrw
left a comment
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 fixing this!
Motivation
This PR adds validation to prevent stack updates when a stack is already deleted or in the process of being deleted (e.g., during deletion). This addresses an issue where users encountered
Programming error: duplicate stacks found. I was able to reproduce it with this process:The root cause was that step 3 didn't properly validate if the found was deleted, leaving both the new stack and the original active in the Cloudformation.
Changes
Testing
create_change_setandupdate_stack