Describe the bug
When I do Vpc.fromLookup in a VPC that has subnets with a default route to a TransitGateway the subnet is detected as PRIVATE_ISOLATED instead of PRIVATE_WITH_EGRESS
This PR that introduced it talks about TransitGateway too but it doesn't seem to get applied.
Expected Behavior
Detect subnet with a default route to a TransitGateway as PRIVATE_WITH_EGRESS
Current Behavior
Subnets with a default route to a TransitGateway are detected as PRIVATE_ISOLATED
Reproduction Steps
Use Vpc.fromLookup in a VPC that has subnets with a default route to a TransitGateway
Possible Solution
No response
Additional Information/Context
No response
CDK CLI Version
2.66
Framework Version
No response
Node.js Version
16.16
OS
MacOS
Language
Typescript
Language Version
No response
Other information
No response
Describe the bug
When I do
Vpc.fromLookupin a VPC that has subnets with a default route to a TransitGateway the subnet is detected asPRIVATE_ISOLATEDinstead ofPRIVATE_WITH_EGRESSThis PR that introduced it talks about TransitGateway too but it doesn't seem to get applied.
Expected Behavior
Detect subnet with a default route to a TransitGateway as
PRIVATE_WITH_EGRESSCurrent Behavior
Subnets with a default route to a TransitGateway are detected as
PRIVATE_ISOLATEDReproduction Steps
Use
Vpc.fromLookupin a VPC that has subnets with a default route to a TransitGatewayPossible Solution
No response
Additional Information/Context
No response
CDK CLI Version
2.66
Framework Version
No response
Node.js Version
16.16
OS
MacOS
Language
Typescript
Language Version
No response
Other information
No response