-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Fix: CFn repeated deployments breaking #11632
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
filter by active stack when executing a changeset use existing store functions to find the changeset check for none revert to loop based filtering
LocalStack Community integration with Pro 2 files ± 0 2 suites ±0 19m 19s ⏱️ - 1h 21m 46s Results for commit 7322e95. ± Comparison against base commit 5d2c090. This pull request removes 3072 and adds 1 tests. Note that renamed tests count towards both.
♻️ This comment has been updated with latest results. |
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.
minor nits, otherwise LGTM!
) -> Optional[StackChangeSet]: | ||
store = get_cloudformation_store(account_id, region_name) | ||
for stack in store.stacks.values(): | ||
if active_only and stack.status == "DELETE_COMPLETE": |
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.
nit: could also reference the value from the generated API here
Co-authored-by: Dominik Schubert <dominik.schubert91@gmail.com>
Motivation
As reported in #11333, performing a deployment of a previously deleted stack fails with the error message:
This is because we don't filter out deleted changesets when looking for a changeset, and therefore assume the changeset already exists and incorrectly fail. Also this only happens when specifying changeset names, which CDK does.
This PR superscedes #11384, however @migraf wrote the initial implementation.
Closes #11333
Changes