feat: Add single_nat_gateway_subnet_index to choose NAT Gateway public subnet #1133
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This PR has been automatically marked as stale because it has been open 30 days |
|
I'm still interested in this feature. |
|
This PR has been automatically marked as stale because it has been open 30 days |
|
I'm still waiting for Senpai to notice me. |
|
This PR has been automatically marked as stale because it has been open 30 days |
|
I'm still waiting for Senpai to notice me. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Add
single_nat_gateway_subnet_indexto choose in which public subnet the single NAT Gateway must be created.Motivation and Context
Currently, the single NAT Gateway is created in the first public subnet and, thus, in the first Availability Zone. This variable allows the user to choose which AZ the NAT Gateway will be created in.
Breaking Changes
This is fully backward compatible and does not introduce any breaking changes.
How Has This Been Tested?
examples/*to demonstrate and validate my change(s)examples/*projectspre-commit run -aon my pull request