-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
google_bigquery_data_transfer_config owner field #20413
Comments
Note from triage: It looks like the API doesn't currently support doing this: https://cloud.google.com/bigquery/docs/reference/datatransfer/rest/v1/projects.locations.transferConfigs There's an Support would need to be added for this at the API level before we could add it into the providers. |
@melinath Thanks for the info. Do I need to take action to get support for this added to the API? |
This has been forwarded to engineering for consideration. There's no particular action you need to take. If you're working with a Google Technical Account Manager or Customer Engineer you can ask them to reach out internally to expedite investigation and resolution of this issue. |
The API is working as intended. According to https://cloud.google.com/bigquery/docs/transfer-run-notifications#email_notifications:
The recommendation is to create a google_pubsub_topic and specify that in |
Per @wj-chen's comment, closing this ticket as resolved. Thanks for reaching out! |
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. |
Community Note
Description
I can set the service_account_name, but I need to be able to set the owner to a group so the users who depend on the scheduled query can get notified if there are failures. I need to be able to set these discreetly and use a google group as the owner while running as a Service Account.
New or Affected Resource(s)
google_bigquery_data_transfer_config
Potential Terraform Configuration
References
No response
b/380890664
The text was updated successfully, but these errors were encountered: