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

Add Notification Options to google_bigquery_data_transfer_config #5866

Closed
samhumphreys-2sixty opened this issue Mar 10, 2020 · 5 comments
Closed

Comments

@samhumphreys-2sixty
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 the issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If the issue is assigned to a user, that user is claiming responsibility for the issue. If the issue is assigned to "hashibot", a community member has claimed the issue already.

Description

The current implementation of google_bigquery_data_transfer_config does not have the option for notifications. In GCP both email and PubSub is supported - it would be great if this was added to the resource.

New or Affected Resource(s)

google_bigquery_data_transfer_config

References

Documentation can be found here - https://cloud.google.com/bigquery-transfer/docs/transfer-run-notifications?#top_of_page

@samhumphreys-2sixty
Copy link
Author

@danawillow /other - Is there any update on this?

@danawillow
Copy link
Contributor

No updates! If you have a google-side customer engineer, TAM, or similar contact, you can ask them to reach out to our team internally for prioritization.

@adamcunnington
Copy link

@danawillow is this now resolved?

@samhumphreys-2sixty
Copy link
Author

Looks like this has been released in 3.37.0. This issue can be closed now 👍

@ghost
Copy link

ghost commented Nov 13, 2020

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 👉 [email protected]. Thanks!

@ghost ghost locked as resolved and limited conversation to collaborators Nov 13, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants