Closed dsdshcym closed 3 years ago
@dsdshcym can you share the full debug log along with the configs for backend service and backend bucket?
@dsdshcym is this still an issue?
Hi @edwardmedia!
Sorry for the late reply.
I can't share the full debug log... But I can share what I found:
url map has not supported regex_match
for an external backend service.
I tested it with gcloud
cli with the following yaml config:
defaultService: backendBucket
kind: compute#urlMap
name: url-map-testing
hostRules:
- hosts:
- "*"
pathMatcher: allpath
pathMatchers:
- defaultService: backendBucket
name: allpath
routeRules:
- matchRules:
- regexMatch: ".*\\.m3u8"
priority: 0
service: externalBackendBucket
and gcloud compute url-maps import ...
returns the same error:
ERROR: (gcloud.compute.url-maps.import) HTTPError 400: Invalid value for field 'resource.pathMatchers[0].routeRules[0].service':'...'. Advanced routing rules are not supported for scheme EXTERNAL
so this issue is not terraform's fault.
I also confirmed that url-rewrite
, query_parameter_matches
and header_matches
now work with external backend services.
I'd wish we can update the route_rules
doc (https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/compute_url_map#route_rules) to make it explicit (it's not fully supported by GCP yet)
@dsdshcym generally the Terraform provider document is based on the GCP APIs. If you found the missing pieces that exist in the API documents, please let us know. Closing this issue then. Feel free to reopen it if you need to continue the conversation
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!
Community Note
modular-magician
user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned tohashibot
, a community member has claimed the issue already.Terraform Version
Affected Resource(s)
google_compute_url_map
google_compute_backend_service
Terraform Configuration Files
Debug Output
Expected Behavior
As @edwardmedia explained in https://github.com/hashicorp/terraform-provider-google/issues/6634#issuecomment-650266253,
So I expect advanced routing rule to be added without an error
Actual Behavior
Tried both provider
google
and providergoogle-beta
, with both providers I got an error like this:Steps to Reproduce
terraform apply
References
6634