Allows secondary_private_ip_address_count to be updated in place#47477
Allows secondary_private_ip_address_count to be updated in place#47477lorengordon wants to merge 1 commit intohashicorp:mainfrom
Conversation
Community GuidelinesThis comment is added to every new Pull Request to provide quick reference to how the Terraform AWS Provider is maintained. Please review the information below, and thank you for contributing to the community that keeps the provider thriving! 🚀 Voting for Prioritization
Pull Request Authors
|
|
✅ Thank you for correcting the previously detected issues! The maintainers appreciate your efforts to make the review process as smooth as possible. |
3b2e6ef to
2ce155a
Compare
0a53c5f to
380168e
Compare
|
Test failures seem unrelated to the changeset. Can someone advise if I need to address them? |
380168e to
4bdfa63
Compare
|
Finding some race conditions when increasing the secondary count. Moving PR to draft while I sort it out. |
4bdfa63 to
786972e
Compare
|
Ok, I think I got it. After way too much troubleshooting, ultimately turned out to be an eventual consistency issue when confirming that the secondary IP addresses had been assigned successfully. Updated the waiter to use |
423ad73 to
49ee8c0
Compare
49ee8c0 to
b92eb3f
Compare
Rollback Plan
If a change needs to be reverted, we will publish an updated version of the library.
Changes to Security Controls
Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.
Description
Updates support for private AWS NAT Gateway to allow
secondary_private_ip_address_countto be updated in placeRelations
Closes #47476
References
Output from Acceptance Testing