feat: Add ability to change client project_id#20767
Conversation
|
🚀 BigQuery Cloud UI deployed to Vercel: |
4284ba1 to
47d0833
Compare
|
Can you please add docs for this to |
…b-creation-permission-error
| * `DATASET_ID` - The Google Cloud BigQuery Dataset ID | ||
|
|
||
| `client_project_id` variable can be used to run BigQuery queries in a project different from where the destination table is located. | ||
| If you set client_project_id to `*detect-project-id*`, it will automatically detect the project ID from the environment variable or application default credentials. No newline at end of file |
There was a problem hiding this comment.
Because that'd change previous behaviour. I.e I'm logged to gcp using user principal which doesn't have project_id set, that'd cause plugin to start failing. Now it is backwards compatible with an option to reconfigure that in spec.
🤖 I have created a release *beep* *boop* --- ## [4.3.0](plugins-destination-bigquery-v4.2.18...plugins-destination-bigquery-v4.3.0) (2025-05-15) ### Features * Add ability to change client project_id ([#20767](#20767)) ([8b9eb98](8b9eb98)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
Summary
In some scenarios users want to execute queries in context of different project than referenced in the query itself. I.e executing pricinipal has permissions to access table in project B only when executing within context of project A. This wasn't possible using only project_id spec. Now default project for execution can also be fetched from the environment/credentials by using
*detect-project-id*variable.