-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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
[Bug]: elbv2/lb: Able to create duplicately named LB #32942
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
This functionality has been released in v5.12.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 issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Terraform Core Version
1.5.5
AWS Provider Version
5.11.0
Affected Resource(s)
Expected Behavior
Should not create when another load balancer already exists with the same name.
Actual Behavior
Right now it is possible to create a load balancer with an aws_lb resource, then (probably accidentally) create another load balancer with the same configuration, but rather than this resulting in a new load balancer, the previously created, existing load balancer is returned. The load balancer is now "managed" by two resources in Terraform, and it is not possible to remove one of them without terraform state rm since removing either of the resources results in deleting the one load balancer.
The accidental "creation" of two Terraform aws_lb resources that manage the same aws_lb, where there is no way to then remove one of them without either destroying the lb or using terraform state rm.
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
Steps to Reproduce
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: