-
Notifications
You must be signed in to change notification settings - Fork 19
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
Feature: add support for execution project on bigquery jobs #183
Comments
It's already supported since 0.2.6 with #164 😉 |
Hey @b-per to be clear, the request is to enable setting this at the job level vs. the connection level. The PR you linked appears to be connection level. Seems there are couple of dependencies here. 1) need to support the ability to set this on the job level in dbt Cloud and 2) enable making that setting via Terraform. |
Ohhh, OK. Let's keep it open then. With extended attributes though it will soon be possible to set it up at the env level in dbt Cloud at least. (and extended attributes should be supported in Terraform soon after they are available in dbt Cloud) |
It is. The docs on the registry actually has a bit more info. |
This issue has been marked as Stale because it has been open for 90 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days. |
This issue has been marked as Stale because it has been open for 90 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days. |
This issue has been marked as Stale because it has been open for 90 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days. |
Bigquery execution project is a key variable for controlling dbt Cloud job spend within bigquery. It would be great if this could be enabled via the provider (community feedback). Feel free to let me know if this a "good first issue" candidate.
The text was updated successfully, but these errors were encountered: