feat(ec2): Require explicit UserData
type instead of string
in Pattern props.
#2378
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.
What does this change?
Updates our EC2 Pattern to require an explicit
UserData
prop instead of astring
. This is part of our work to enable Cloudformation Replace deployments in our ASG.This is a BREAKING change as applications relying on the type being a
string
will need to make a code change in order to update their GuCDK version.Details on this change can be found in the included changeset file: .changeset/thick-owls-remain.md