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
Sorry, I wrote a really long description with details, but then this page crashed and all was lost. So here is the quick summary:
I cannot use google_tags_tag_binding or google_tags_location_tag_binding to bind to a resource with a location if that resource is multi-region. I discovered this with BigQuery datasets, but it's probably true with other multi-regional resources like Pub/Sub.
This is not a Google issue, because I was able to successfully do this via gcloud:
Community Note
Description
Sorry, I wrote a really long description with details, but then this page crashed and all was lost. So here is the quick summary:
I cannot use
google_tags_tag_binding
orgoogle_tags_location_tag_binding
to bind to a resource with a location if that resource is multi-region. I discovered this with BigQuery datasets, but it's probably true with other multi-regional resources like Pub/Sub.This is not a Google issue, because I was able to successfully do this via
gcloud
:New or Affected Resource(s)
google_tags_location_tag_binding google_tags_tag_binding google_tags_tag_value google_bigquery_dataset
Potential Terraform Configuration
I don't think anything further is needed. I think that
google_tags_location_tag_binding
just needs to be amended so that it can manage multi-region.References
No response
b/343221074