Add static route to spoke subnet that is not attached to TGW

[ckamps]

Is your feature request related to a problem? Please describe.

Apparent inability to configure the solution to automatically add a subnet route table for a subnet that is not attached to the TGW.

Describe the feature you'd like

In the following diagram, I'd like a means to configure the solution so that the route in the public subnet route tables of the egress VPC is automatically added. In this example, the route table entry would be 172.16.0.0/12 -> TGW to route traffic returned from the internet through the NAT GW back through to the TGW.

In this example, the egress VPC's private subnets are attached to the TGW.

[bassemwanis]

Thank you @ckamps, for requesting this feature. We've added it to our backlog and will carefully evaluate it. We will keep you updated on any decisions regarding the issue.