Draft
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. |
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
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.
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