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 support for BigQuery Scheduling Queries #2028

Closed
marcin-kolda opened this issue Sep 11, 2018 · 3 comments · Fixed by GoogleCloudPlatform/magic-modules#2100
Closed

Add support for BigQuery Scheduling Queries #2028

marcin-kolda opened this issue Sep 11, 2018 · 3 comments · Fixed by GoogleCloudPlatform/magic-modules#2100

Comments

@marcin-kolda
Copy link
Contributor

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

Add support for BigQuery Scheduling Queries. It would be great to have scheduled queries created in TF on top of BigQuery views or tables, e.g. when you setup new app, you can create tables, views and queries which could do some periodical aggregation, etc.

New or Affected Resource(s)

  • google_bigquery_scheduled_query
@ghost ghost added the enhancement label Sep 11, 2018
@cemo
Copy link

cemo commented Mar 28, 2019

Is there something blocking this issue? Since the release of 2.0.0 (February 12, 2019), there is only single new terraform resource. I really can not understand how things are prioritised. BigQuery is the most important part of Google Cloud when it is compared with others but there are waiting many improvements and new resources related to it.

@danawillow
Copy link
Contributor

I think the API that this request is looking at is this one: https://cloud.google.com/bigquery/docs/reference/datatransfer/rest/v1/projects.locations.transferConfigs, though there's going to be some design work there to figure out how closely to map that vs what is seen in the console (the "params" field being the biggest difference, since there are no guidelines that I can find about what actually goes there, though I'm pretty sure one of the things would be the query to schedule).

@cemo to answer your question, our team does many things besides just creating new resources: we add new capabilities to old ones, fix bugs, do infrastructure improvements, review incoming PRs, and also spend time on other things that come up, like making sure the provider was compatible with 0.12. I recognize that it's frustrating not to see the features you want. If you have someone at GCP or HashiCorp (an account manager, sales rep, customer engineer, etc.) that you work with, feel free to contact them about the features you're looking for. Alternatively, we happily accept PRs against the provider, though for new resources like this we prefer to generate them with magic modules.

@ghost
Copy link

ghost commented Sep 13, 2019

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 👉 hashibot-feedback@hashicorp.com. Thanks!

@ghost ghost locked and limited conversation to collaborators Sep 13, 2019
@github-actions github-actions bot added service/bigquery forward/review In review; remove label to forward labels Jan 14, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants