Skip to content
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

Terraform support for Wildcard Path Matching and Rewrites of Regional HTTP(S) Load Balancers #17545

Comments

@rostislavbobo
Copy link

Community Note

  • 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

Add support for the new flexible pattern matching of Regional HTTP(S) Load Balancers, now globally available. Read more about URL Map wildcards matching at https://cloud.google.com/load-balancing/docs/url-map-concepts?hl=en#wildcards-regx-dynamic-route.

New or Affected Resource(s)

  • google_compute_region_url_map: path_template_match = string
  • google_compute_region_url_map: path_template_rewrite = string

Potential Terraform Configuration

Configuration is similar to the Url Map Path Template Match.

References

Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 13, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.