-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
CFn(chore): refactor post-deploy steps #13242
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 48m 9s ⏱️ For more details on these failures, see this check. Results for commit 3449b53. ♻️ This comment has been updated with latest results. |
Test Results - Alternative Providers580 tests 330 ✅ 25m 19s ⏱️ Results for commit 3449b53. ♻️ This comment has been updated with latest results. |
LocalStack Community integration with Pro 2 files ± 0 2 suites ±0 35m 18s ⏱️ - 1h 27m 22s For more details on these failures, see this check. Results for commit 3449b53. ± Comparison against base commit b2694a8. This pull request removes 4227 tests.♻️ This comment has been updated with latest results. |
Motivation
We have multiple places where after a change set execution, we need to propagate state back to the parent stack. These places are:
execute_change_setcreate_stackupdate_stackdelete_stack(sort of)These should probably have the same behaviour to make sure we don't forget to propagate state somewhere
Changes