Closed RunCor399 closed 2 months ago
how has this been tested and validated
how has this been tested and validated
I have run the same example quoted in issue #1061 before and after my modification.
Maybe it makes sense to set create_egress_only_igw
to false by default?
Maybe it makes sense to set
create_egress_only_igw
to false by default?
I believe that since create_egress_only_igw
is also used in the database_ipv6_egress
route, setting it to false by default may cause problems when having a setup with database subnets and no private subnets (and viceversa). In the latter scenario create_egress_only_igw
would have to be set to true, thus leading to the creation of routes for both private and db subnets
This PR is included in version 5.7.2 :tada:
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Description
Private IPv6 Egress routes are now only created when having at least a private subnet
Motivation and Context
Version 5.7.1 of the module solved the issue #1058 by limiting the amount of IPv6 egress routes created to the amount of NAT gateways provisioned (hence to the amount of Route Tables created).
However the condition that regulates the number of IPv6 egress routes created doesn't check if the creation of any private subnet is actually wanted
Breaking Changes
How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)examples/*
projectspre-commit run -a
on my pull request