This PR sees that the aws-cdk:subnet-name and aws-cdk:subnet-type tags are added to all provisioned subnets. These tags are require by AWS CDK for resolving subnets on an existing deployed VPCs. See the docs for further details.
Types of changes
What types of changes does your code introduce to ?
Put an x in the boxes that apply
[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)
Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.
[x] I have read the CONTRIBUTING.md doc.
[x] I have added necessary documentation (if appropriate).
[x] Any dependent changes have been merged and published in downstream modules.
Further comments
It's up for debate as to whether or not we add these tags based if a specific boolean variable is defined.
This PR sees that the
aws-cdk:subnet-nameandaws-cdk:subnet-typetags are added to all provisioned subnets. These tags are require by AWS CDK for resolving subnets on an existing deployed VPCs. See the docs for further details.Types of changes
What types of changes does your code introduce to?
Put an
xin the boxes that applyChecklist
Put an
xin the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.Further comments
It's up for debate as to whether or not we add these tags based if a specific boolean variable is defined.