feat: Make the enable_nat_gateway and single_nat_gateway variables configurable #343
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Our team recently received an email from AWS recommending the utilization of separate NAT Gateways per AZ, and we tracked down the VPC / NAT Gateway combinations to be coming from our usage of the atlantis module.
This PR adds variables to configure the arguments
enable_nat_gateway
andsingle_nat_gateway
to theterraform-aws-modules/vpc/aws
submodule.Motivation and Context
This change is in direct response to the following message we received from AWS, via e-mail:
Breaking Changes
No changes. All new variables are optional, and I set the newly added variables to default to the same initial values as before.
How Has This Been Tested?
We are using this in our own AWS environment.