-
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
aws_lb_target_group protocol_version update should destroy/create #17797
Comments
Relates: The diff is being suppressed here: terraform-provider-aws/aws/resource_aws_lb_target_group.go Lines 89 to 97 in 7546a7f
|
We ran into a similar issue. We are trying to change |
Same here: Had to use |
This functionality has been released in v4.50.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. |
Affected Resource(s)
aws_lb_target_group
Using
3.27.0
.Expected Behavior
Changing property
protocol_version
fromGRPC
toHTTP2
should trigger a destroy/create.Actual Behavior
TF wants to modify the resource.
When applied, no error occurs but the value is not updated, and another plan wants to apply the update again.
In my case, I did change the healthcheck endpoint at the same time, expecting the updated protocol would be used. The endpoint was changed but not the protocol, healtchcheck failed and my ASG was drained 💥
Steps to Reproduce
Create a resource
aws_lb_target_group
withprotocol_version
=GRPC
then update toHTTP2
and notice the change is not applied.The text was updated successfully, but these errors were encountered: