-
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
resource aws_globalaccelerator_endpoint_group is not up-to-date after apply #9329
Comments
Workaround:
It would probably make sense to remove the default "/" value to be more in line with the implementation of similar resources, e.g. |
Hi folks 👋 This does indeed look like an issue in the resource schema, where we default the value to For reference, the
The simplest fix in these cases is to switch from * `health_check_path` - (Optional) If the protocol is HTTP/S, then this specifies the path that is the destination for health check targets. The default value is slash (/) for HTTP/S and undeclared for TCP. Terraform will only perform drift detection of its value when present in a configuration. If anyone is interested in implementing and verifying the fix, we will be happy to take a look. 👍 See also the Contributing Guide section on running acceptance testing. |
The fix for this has been merged and will release with version 3.4.0 of the Terraform AWS Provider, later next week. 👍 |
This has been released in version 3.4.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 for triage. Thanks! |
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. |
Community Note
Terraform Version
Affected Resource(s)
Terraform Configuration Files
Debug Output
Panic Output
Expected Behavior
after applying my changes i expect further runs of terraform plan or terraform apply to be up-to-date
Actual Behavior
after applying my changes terraform does not consider the resources to be up-to-date. running terraform apply again will again modify the resource.
Steps to Reproduce
Note that it is trying to modify health_check_path.
Important Factoids
Note that there is no mention of health check path here.
References
The text was updated successfully, but these errors were encountered: