Closed gservat closed 1 month ago
Confirmed issue!
If the google_compute_region_target_https_proxy
resource already exists after create or use the google_network_security_server_tls_policy
resource in the current terraform configuration then returns the next error message:
Error: Error when reading or editing RegionTargetHttpsProxy: googleapi: Error 400: The target_https_proxy resource 'projects/<project>/regions/us-central1/targetHttpsProxies/https-proxy' is already being used by 'projects/<project>/regions/us-central1/forwardingRules/https-frwd-rule', resourceInUseByAnotherResource
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. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Community Note
Terraform Version & Provider Version(s)
Terraform v1.9.2 on arm64
Affected Resource(s)
google_compute_region_target_https_proxy
Terraform Configuration
Debug Output
No response
Expected Behavior
The update to enable
server_tls_policy
on the target HTTPS proxy applies cleanly and does not re-create the target HTTPS proxy as this is supported by Google's API toPATCH
the resource.Actual Behavior
It attempts to recreate the HTTPS proxy but fails because there is a forwarding rule attached to the proxy:
Steps to reproduce
terraform apply
original TF configterraform apply
updated TF config with the server TLS policyImportant Factoids
No response
References
Similar issue to https://github.com/hashicorp/terraform-provider-google/issues/16963 except this concerns the
server_tls_policy
vsssl_policy
.b/355116824
b/355124984