-
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]: resource/aws_lb_target_group - Forces replacement of resource after importing #27463
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Relates #26320. |
Being picked up by @brittandeyoung in #27464 |
This functionality has been released in v4.37.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.3.3
AWS Provider Version
4.36.1
Affected Resource(s)
Expected Behavior
After importing the existing IP target group(IPv4 address type), it should be safe from replacement by Terraform.
Actual Behavior
After importing the existing IP target group(IPv4 address type), Terraform always makes a plan to forcibly replace the target group.
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
Steps to Reproduce
terraform plan
.Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
Would you like to implement a fix?
No response
The text was updated successfully, but these errors were encountered: