You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 馃憤 reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
If an issue is assigned to a user, that user is claiming responsibility for the issue.
Customers working with a Google Technical Account Manager or Customer Engineer can ask them to reach out internally to expedite investigation and resolution of this issue.
Description
For a while it has been possible to create custom error responses on external application load balancers. The terraform provider for this resource hasn't been updated with this functionality yet.
Both google_compute_url_map and google_compute_region_url_map support defaultCustomErrorResponsePolicy Will add it to the regional resource as well.
I am refraining from doing the google_compute_region_url_map to unblock @RubenAtBinx. The errorService field is not supported for regional/internal HTTPS load balancers as stated by the API, however, somehow i can't get it to work with a regional url map in any way. It says the errorService needs a bucket as a target but the backends for buckets are always global, and that one is unexpected for regional url maps.
Community Note
Description
For a while it has been possible to create custom error responses on external application load balancers. The terraform provider for this resource hasn't been updated with this functionality yet.
https://cloud.google.com/load-balancing/docs/https/configure-custom-error-responses
New or Affected Resource(s)
Potential Terraform Configuration
References
No response
b/341993855
The text was updated successfully, but these errors were encountered: