v0.2.5 - Allow import of Transit Gateway peers and ability to reference in the VPC Routes.

• Allow the import of Transit Gateway Peers in the configuration file.
• Allow use of Transit Gateway Peers as 'routesTo' in the routing sections for VPCs (note only static routes, and default routes are supported by peers).
• See the Config file Walkthrough for details and syntax.

v0.2.4 - Bug fix for Direct Connect Gateway Propagations

• Fix missing attribute on the DX GW model that erroneously determined it was not attached to a Transit Gateway and automatically establishing a return path.

v0.2.3 - Improved interface endpoint region handling and documentation

• Interface Endpoint list parsing now 'does what I mean' by substituting any present region string with the region specified in the global section of the configuration file.
• Improved documentation around interface endpoints and regional considerations
• Version bump on CDK and Libraries
• Updated discovery material for interface endpoint parsing

Bug Fixes

• Fixed a bug where a provider that is vpc based is considered invalid within a vpcName: route
• Updated test cases to include synthesis of all available configuration files.
• Updated tests to run for Node 18 and 20 instead of 16 and 18 (16 is no deprecated)

v0.2.1 - Use of VPC Names in BlackHole Routes and fixes

You can now use a VPC Name from the configuration file as a blackholeCidr. The vpcCidr will automatically be substituted for you. This should improve readability of the configuration file where blackhole configurations are between vpcBuilder defined VPCs.

Includes a bug fix to RAM Shared subnets. They will now be named with the VPC Name instead of just the VPC Style making it easier to understand what share relates to what VPC.

v0.2.0 - Support for DxGw and fixes

• Fix for RAM sharing issues #15
• Support for modelling a Direct Connect Transit Gateway permitting use in routesTo: #20

Release 0.1.0

Initial release.