Draft
Conversation
simonrw
added
the
semver: patch
simonrw
force-pushed
the
cfn/v2/validated-stack-sets
branch
from
b97c752 to
125103f
Compare
Test Results (amd64) - Integration, Bootstrap 5 files 5 suites 2h 20m 29s ⏱️ Results for commit 125103f. |
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
3 participants
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
With #12909 we introduced stack set support, however the test was not enough and did not actually test the resources in the stack instances were actually created.
I originally didn't think this was possible and required manual setup, however in a classic shower thought I realised I could ensure the "manual" setup could be done via a CFn template.
Changes