resourceop: deploy all CDK stacks by default #53
Merged
Conversation
This file contains 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
The `Name` within `Stacks` go struct has caused confusion so we default to deploying all CDK stacks so that the Name can be used alongside terraform stacks and filter.
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.
The
NamewithinStacksgo struct has caused confusion so we default to deploying all CDK stacks so that the Name can be used alongside terraform stacks and filter.The original intention of
Namewas to be able to target CDK stacks, but we want to provide filtering on terraform and cdk stacks. We can always add back CDK stack filtering by allowing an end user to pass in additional flags to the CDK or specifying CDKStacks. For now, we are removing the feature