-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
b/aws_eip reverse network_border_group change introduced by PR #39604 #39642
b/aws_eip reverse network_border_group change introduced by PR #39604 #39642
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.
LGTM 🚀.
Thank you for your contribution! 🚀 Please note that typically Go dependency changes are handled in this repository by dependabot or the maintainers. This is to prevent pull request merge conflicts and further delay reviews of contributions. Remove any changes to the Additional details:
|
@alexbacchin Thanks for the contribution 🎉 👏. |
This functionality has been released in v5.72.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
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. |
Description
This reverse an unintentional change that was merged. The
network_border_group
argument was set toForceNew: true
before PR. However, I mistakenly removed this configuration when raised #39604.Relations
Relates #39604
References
https://github.com/hashicorp/terraform-provider-aws/pull/39604/files#diff-04d832a3ddac3fea572439b0bd9ee1f3d4dcf58a7d3331fd00c7b872ca17b0c5L103
Output from Acceptance Testing