-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FIX: aws_nat_gateway
resource secondary_private_ip_address_count
logic
#36360
base: main
Are you sure you want to change the base?
Conversation
Community NoteVoting for Prioritization
For Submitters
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Welcome @davidsonjon 👋
It looks like this is your first Pull Request submission to the Terraform AWS Provider! If you haven’t already done so please make sure you have checked out our CONTRIBUTOR guide and FAQ to make sure your contribution is adhering to best practice and has all the necessary elements in place for a successful approval.
Also take a look at our FAQ which details how we prioritize Pull Requests for inclusion.
Thanks again, and welcome to the community! 😃
Any update on when this can get merged? |
Would also love to see this merged, I'd be happy to help in any way I could in order to expedite. |
Hi, can this be merged ASAP? I'm also happy to test if something is needed. I have a really big cluster with githubrunners that needs seconmdary IP's and I'm totally blocked due to this because when enabling it it has downtime. Thanks in advance to anyone who can make this go forward asap. |
@justinretzolk Hi, could you take a look or ping someone to review and hopefully approve this PR? This is really important, as right now natgw's get recreated everytime we run terraform with secondary IP's enabled (even when no changes happen) making it basically unusable in production systems as it causes downtime. This fix is absolutely critical. Thanks |
When will this be resolved? This is a bug that needs to be fixed immediately. |
I am having trouble with secondary_private_ip_address_count also, this PR is super important. |
Description
Move logic for
secondary_private_ip_address_count
forforceNew
to customizeDiffRelations
Closes #33964
Output from Acceptance Testing
I am unable to run the tests in my organization due to VPC limits, so some help would be appreciated but I was able to run the following tests
From the use case in #33964 adding
secondary_allocation_ids
to and existing configuration yieldsRemoving
secondary_allocation_ids
Changing
secondary_private_ip_address_count
yields the following plan