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

Feature: add support for execution project on bigquery jobs #183

Open
matt-winkler opened this issue Aug 22, 2023 · 8 comments
Open

Feature: add support for execution project on bigquery jobs #183

matt-winkler opened this issue Aug 22, 2023 · 8 comments
Labels

Comments

@matt-winkler
Copy link

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.

@b-per
Copy link
Collaborator

b-per commented Aug 28, 2023

It's already supported since 0.2.6 with #164 😉

@b-per b-per closed this as completed Aug 28, 2023
@matt-winkler
Copy link
Author

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.

@matt-winkler matt-winkler reopened this Sep 5, 2023
@b-per
Copy link
Collaborator

b-per commented Sep 5, 2023

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)

@b-per b-per added the blocked label Sep 18, 2023
@matt-winkler
Copy link
Author

Hey @b-per can you confirm this is the extended attributes setting at the environment level? Looks like it just would appreciate a quick yes / no.

@b-per
Copy link
Collaborator

b-per commented Oct 31, 2023

It is. The docs on the registry actually has a bit more info.

Copy link

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.

@github-actions github-actions bot added the stale label Jan 30, 2024
@b-per b-per removed the stale label Jan 30, 2024
Copy link

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.

@github-actions github-actions bot added the stale label Apr 30, 2024
@b-per b-per removed the stale label Apr 30, 2024
Copy link

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.

@github-actions github-actions bot added the stale label Jul 30, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 6, 2024
@b-per b-per reopened this Aug 12, 2024
@b-per b-per removed the stale label Aug 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants