fix(bigquery): add impersonateServiceAccount to prebuilt config#2770
Merged
duwenxin99 merged 3 commits intogoogleapis:mainfrom Mar 27, 2026
Merged
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
Contributor
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request enhances the prebuilt BigQuery configuration by integrating support for service account impersonation via an environment variable. This change addresses a significant pain point for users who previously had to abandon the convenient prebuilt configurations and manually redefine all tools just to enable impersonation, particularly beneficial for organizations using impersonation for AI agent permission scoping. Highlights
Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request correctly adds support for service account impersonation via the BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT environment variable in the prebuilt BigQuery configuration. The change is a simple and effective addition to internal/prebuiltconfigs/tools/bigquery.yaml. While the code change is correct, the documentation should be updated to reflect this new configuration option. Specifically, docs/BIGQUERY_README.md should be updated to include BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT in the list of environment variables for the prebuilt server.
duwenxin99
approved these changes
Mar 18, 2026
Contributor
|
/gcbrun |
Contributor
duwenxin99
added
the
priority: p2
Contributor
Contributor
|
Hi @kwkeefer , do you mind resolving this conflict? Thank you! |
added 2 commits
March 26, 2026 15:54
Add BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT env var to the prebuilt BigQuery YAML so users can enable service account impersonation without replacing --prebuilt with a custom --tools-file.
…d to document the new env var
auto-merge was automatically disabled
March 26, 2026 22:57
Head branch was pushed to by a user without write access
kwkeefer
force-pushed
the
bigquery-prebuilt-impersonate-sa
branch
from
8053069 to
59607bd
Compare
Contributor
Author
|
@Yuan325 done |
Contributor
|
/gcbrun |
Contributor
|
🚀 Cloudflare Preview Ready! 🔎 View Preview: https://pr-2770.toolbox-docs-6xc.pages.dev (Note: Subsequent pushes to this PR will automatically update the preview at this same URL) |
Contributor
github-actions bot
pushed a commit
that referenced
this pull request
Mar 27, 2026
…ig (#2770) ## Summary Add `BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT` env var support to the prebuilt BigQuery configuration, enabling service account impersonation without requiring a custom `--tools-file`. ## Problem The BigQuery source already supports `impersonateServiceAccount` (added in #1641 / #906), but the prebuilt config at `internal/prebuiltconfigs/tools/bigquery.yaml` does not expose it via an environment variable. This forces users who need impersonation to abandon `--prebuilt bigquery` entirely and create a custom `--tools-file` that manually redefines all 9 tools — just to set one field on the source. This is a common need for organizations that use service account impersonation to scope permissions for AI agents, rather than granting broad access to individual user accounts. ## Solution Add a single line to the prebuilt BigQuery YAML: ```yaml impersonateServiceAccount: ${BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT:} ``` The empty default (`:`) means existing users are unaffected — the field is ignored when the env var is not set, preserving full backward compatibility. ## Validation Built the patched binary locally and confirmed: - Without the env var: `SESSION_USER()` returns the personal account (unchanged behavior) - With the env var: `SESSION_USER()` returns the impersonated service account ## PR Checklist - [x] Make sure you reviewed [CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md) - [x] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [x] Ensure the tests and linter pass - [x] Code coverage does not decrease (if any source code was changed) - [x] Appropriate docs were updated (if necessary) - [x] Make sure to add `!` if this involve a breaking change 🛠️ Fixes #2769 --------- Co-authored-by: kkeefer1 <kyle_keefer@intuit.com> Co-authored-by: Wenxin Du <117315983+duwenxin99@users.noreply.github.com> 9c3a748
github-actions bot
pushed a commit
that referenced
this pull request
Mar 27, 2026
…ig (#2770) ## Summary Add `BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT` env var support to the prebuilt BigQuery configuration, enabling service account impersonation without requiring a custom `--tools-file`. ## Problem The BigQuery source already supports `impersonateServiceAccount` (added in #1641 / #906), but the prebuilt config at `internal/prebuiltconfigs/tools/bigquery.yaml` does not expose it via an environment variable. This forces users who need impersonation to abandon `--prebuilt bigquery` entirely and create a custom `--tools-file` that manually redefines all 9 tools — just to set one field on the source. This is a common need for organizations that use service account impersonation to scope permissions for AI agents, rather than granting broad access to individual user accounts. ## Solution Add a single line to the prebuilt BigQuery YAML: ```yaml impersonateServiceAccount: ${BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT:} ``` The empty default (`:`) means existing users are unaffected — the field is ignored when the env var is not set, preserving full backward compatibility. ## Validation Built the patched binary locally and confirmed: - Without the env var: `SESSION_USER()` returns the personal account (unchanged behavior) - With the env var: `SESSION_USER()` returns the impersonated service account ## PR Checklist - [x] Make sure you reviewed [CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md) - [x] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [x] Ensure the tests and linter pass - [x] Code coverage does not decrease (if any source code was changed) - [x] Appropriate docs were updated (if necessary) - [x] Make sure to add `!` if this involve a breaking change 🛠️ Fixes #2769 --------- Co-authored-by: kkeefer1 <kyle_keefer@intuit.com> Co-authored-by: Wenxin Du <117315983+duwenxin99@users.noreply.github.com> 9c3a748
github-actions bot
pushed a commit
to renovate-bot/googleapis-_-genai-toolbox
that referenced
this pull request
Mar 27, 2026
…ig (googleapis#2770) ## Summary Add `BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT` env var support to the prebuilt BigQuery configuration, enabling service account impersonation without requiring a custom `--tools-file`. ## Problem The BigQuery source already supports `impersonateServiceAccount` (added in googleapis#1641 / googleapis#906), but the prebuilt config at `internal/prebuiltconfigs/tools/bigquery.yaml` does not expose it via an environment variable. This forces users who need impersonation to abandon `--prebuilt bigquery` entirely and create a custom `--tools-file` that manually redefines all 9 tools — just to set one field on the source. This is a common need for organizations that use service account impersonation to scope permissions for AI agents, rather than granting broad access to individual user accounts. ## Solution Add a single line to the prebuilt BigQuery YAML: ```yaml impersonateServiceAccount: ${BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT:} ``` The empty default (`:`) means existing users are unaffected — the field is ignored when the env var is not set, preserving full backward compatibility. ## Validation Built the patched binary locally and confirmed: - Without the env var: `SESSION_USER()` returns the personal account (unchanged behavior) - With the env var: `SESSION_USER()` returns the impersonated service account ## PR Checklist - [x] Make sure you reviewed [CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md) - [x] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [x] Ensure the tests and linter pass - [x] Code coverage does not decrease (if any source code was changed) - [x] Appropriate docs were updated (if necessary) - [x] Make sure to add `!` if this involve a breaking change 🛠️ Fixes googleapis#2769 --------- Co-authored-by: kkeefer1 <kyle_keefer@intuit.com> Co-authored-by: Wenxin Du <117315983+duwenxin99@users.noreply.github.com> 9c3a748
github-actions bot
pushed a commit
to renovate-bot/googleapis-_-genai-toolbox
that referenced
this pull request
Mar 27, 2026
…ig (googleapis#2770) ## Summary Add `BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT` env var support to the prebuilt BigQuery configuration, enabling service account impersonation without requiring a custom `--tools-file`. ## Problem The BigQuery source already supports `impersonateServiceAccount` (added in googleapis#1641 / googleapis#906), but the prebuilt config at `internal/prebuiltconfigs/tools/bigquery.yaml` does not expose it via an environment variable. This forces users who need impersonation to abandon `--prebuilt bigquery` entirely and create a custom `--tools-file` that manually redefines all 9 tools — just to set one field on the source. This is a common need for organizations that use service account impersonation to scope permissions for AI agents, rather than granting broad access to individual user accounts. ## Solution Add a single line to the prebuilt BigQuery YAML: ```yaml impersonateServiceAccount: ${BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT:} ``` The empty default (`:`) means existing users are unaffected — the field is ignored when the env var is not set, preserving full backward compatibility. ## Validation Built the patched binary locally and confirmed: - Without the env var: `SESSION_USER()` returns the personal account (unchanged behavior) - With the env var: `SESSION_USER()` returns the impersonated service account ## PR Checklist - [x] Make sure you reviewed [CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md) - [x] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [x] Ensure the tests and linter pass - [x] Code coverage does not decrease (if any source code was changed) - [x] Appropriate docs were updated (if necessary) - [x] Make sure to add `!` if this involve a breaking change 🛠️ Fixes googleapis#2769 --------- Co-authored-by: kkeefer1 <kyle_keefer@intuit.com> Co-authored-by: Wenxin Du <117315983+duwenxin99@users.noreply.github.com> 9c3a748
github-actions bot
pushed a commit
to pepe57/genai-toolbox
that referenced
this pull request
Mar 27, 2026
…ig (googleapis#2770) ## Summary Add `BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT` env var support to the prebuilt BigQuery configuration, enabling service account impersonation without requiring a custom `--tools-file`. ## Problem The BigQuery source already supports `impersonateServiceAccount` (added in googleapis#1641 / googleapis#906), but the prebuilt config at `internal/prebuiltconfigs/tools/bigquery.yaml` does not expose it via an environment variable. This forces users who need impersonation to abandon `--prebuilt bigquery` entirely and create a custom `--tools-file` that manually redefines all 9 tools — just to set one field on the source. This is a common need for organizations that use service account impersonation to scope permissions for AI agents, rather than granting broad access to individual user accounts. ## Solution Add a single line to the prebuilt BigQuery YAML: ```yaml impersonateServiceAccount: ${BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT:} ``` The empty default (`:`) means existing users are unaffected — the field is ignored when the env var is not set, preserving full backward compatibility. ## Validation Built the patched binary locally and confirmed: - Without the env var: `SESSION_USER()` returns the personal account (unchanged behavior) - With the env var: `SESSION_USER()` returns the impersonated service account ## PR Checklist - [x] Make sure you reviewed [CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md) - [x] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [x] Ensure the tests and linter pass - [x] Code coverage does not decrease (if any source code was changed) - [x] Appropriate docs were updated (if necessary) - [x] Make sure to add `!` if this involve a breaking change 🛠️ Fixes googleapis#2769 --------- Co-authored-by: kkeefer1 <kyle_keefer@intuit.com> Co-authored-by: Wenxin Du <117315983+duwenxin99@users.noreply.github.com> 9c3a748
github-actions bot
pushed a commit
to pepe57/genai-toolbox
that referenced
this pull request
Mar 27, 2026
…ig (googleapis#2770) ## Summary Add `BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT` env var support to the prebuilt BigQuery configuration, enabling service account impersonation without requiring a custom `--tools-file`. ## Problem The BigQuery source already supports `impersonateServiceAccount` (added in googleapis#1641 / googleapis#906), but the prebuilt config at `internal/prebuiltconfigs/tools/bigquery.yaml` does not expose it via an environment variable. This forces users who need impersonation to abandon `--prebuilt bigquery` entirely and create a custom `--tools-file` that manually redefines all 9 tools — just to set one field on the source. This is a common need for organizations that use service account impersonation to scope permissions for AI agents, rather than granting broad access to individual user accounts. ## Solution Add a single line to the prebuilt BigQuery YAML: ```yaml impersonateServiceAccount: ${BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT:} ``` The empty default (`:`) means existing users are unaffected — the field is ignored when the env var is not set, preserving full backward compatibility. ## Validation Built the patched binary locally and confirmed: - Without the env var: `SESSION_USER()` returns the personal account (unchanged behavior) - With the env var: `SESSION_USER()` returns the impersonated service account ## PR Checklist - [x] Make sure you reviewed [CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md) - [x] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [x] Ensure the tests and linter pass - [x] Code coverage does not decrease (if any source code was changed) - [x] Appropriate docs were updated (if necessary) - [x] Make sure to add `!` if this involve a breaking change 🛠️ Fixes googleapis#2769 --------- Co-authored-by: kkeefer1 <kyle_keefer@intuit.com> Co-authored-by: Wenxin Du <117315983+duwenxin99@users.noreply.github.com> 9c3a748
github-actions bot
pushed a commit
to Jaleel-zhu/genai-toolbox
that referenced
this pull request
Mar 27, 2026
…ig (googleapis#2770) ## Summary Add `BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT` env var support to the prebuilt BigQuery configuration, enabling service account impersonation without requiring a custom `--tools-file`. ## Problem The BigQuery source already supports `impersonateServiceAccount` (added in googleapis#1641 / googleapis#906), but the prebuilt config at `internal/prebuiltconfigs/tools/bigquery.yaml` does not expose it via an environment variable. This forces users who need impersonation to abandon `--prebuilt bigquery` entirely and create a custom `--tools-file` that manually redefines all 9 tools — just to set one field on the source. This is a common need for organizations that use service account impersonation to scope permissions for AI agents, rather than granting broad access to individual user accounts. ## Solution Add a single line to the prebuilt BigQuery YAML: ```yaml impersonateServiceAccount: ${BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT:} ``` The empty default (`:`) means existing users are unaffected — the field is ignored when the env var is not set, preserving full backward compatibility. ## Validation Built the patched binary locally and confirmed: - Without the env var: `SESSION_USER()` returns the personal account (unchanged behavior) - With the env var: `SESSION_USER()` returns the impersonated service account ## PR Checklist - [x] Make sure you reviewed [CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md) - [x] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [x] Ensure the tests and linter pass - [x] Code coverage does not decrease (if any source code was changed) - [x] Appropriate docs were updated (if necessary) - [x] Make sure to add `!` if this involve a breaking change 🛠️ Fixes googleapis#2769 --------- Co-authored-by: kkeefer1 <kyle_keefer@intuit.com> Co-authored-by: Wenxin Du <117315983+duwenxin99@users.noreply.github.com> 9c3a748
github-actions bot
pushed a commit
to Jaleel-zhu/genai-toolbox
that referenced
this pull request
Mar 27, 2026
…ig (googleapis#2770) ## Summary Add `BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT` env var support to the prebuilt BigQuery configuration, enabling service account impersonation without requiring a custom `--tools-file`. ## Problem The BigQuery source already supports `impersonateServiceAccount` (added in googleapis#1641 / googleapis#906), but the prebuilt config at `internal/prebuiltconfigs/tools/bigquery.yaml` does not expose it via an environment variable. This forces users who need impersonation to abandon `--prebuilt bigquery` entirely and create a custom `--tools-file` that manually redefines all 9 tools — just to set one field on the source. This is a common need for organizations that use service account impersonation to scope permissions for AI agents, rather than granting broad access to individual user accounts. ## Solution Add a single line to the prebuilt BigQuery YAML: ```yaml impersonateServiceAccount: ${BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT:} ``` The empty default (`:`) means existing users are unaffected — the field is ignored when the env var is not set, preserving full backward compatibility. ## Validation Built the patched binary locally and confirmed: - Without the env var: `SESSION_USER()` returns the personal account (unchanged behavior) - With the env var: `SESSION_USER()` returns the impersonated service account ## PR Checklist - [x] Make sure you reviewed [CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md) - [x] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [x] Ensure the tests and linter pass - [x] Code coverage does not decrease (if any source code was changed) - [x] Appropriate docs were updated (if necessary) - [x] Make sure to add `!` if this involve a breaking change 🛠️ Fixes googleapis#2769 --------- Co-authored-by: kkeefer1 <kyle_keefer@intuit.com> Co-authored-by: Wenxin Du <117315983+duwenxin99@users.noreply.github.com> 9c3a748
github-actions bot
pushed a commit
to xaas-cloud/genai-toolbox
that referenced
this pull request
Mar 28, 2026
…ig (googleapis#2770) ## Summary Add `BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT` env var support to the prebuilt BigQuery configuration, enabling service account impersonation without requiring a custom `--tools-file`. ## Problem The BigQuery source already supports `impersonateServiceAccount` (added in googleapis#1641 / googleapis#906), but the prebuilt config at `internal/prebuiltconfigs/tools/bigquery.yaml` does not expose it via an environment variable. This forces users who need impersonation to abandon `--prebuilt bigquery` entirely and create a custom `--tools-file` that manually redefines all 9 tools — just to set one field on the source. This is a common need for organizations that use service account impersonation to scope permissions for AI agents, rather than granting broad access to individual user accounts. ## Solution Add a single line to the prebuilt BigQuery YAML: ```yaml impersonateServiceAccount: ${BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT:} ``` The empty default (`:`) means existing users are unaffected — the field is ignored when the env var is not set, preserving full backward compatibility. ## Validation Built the patched binary locally and confirmed: - Without the env var: `SESSION_USER()` returns the personal account (unchanged behavior) - With the env var: `SESSION_USER()` returns the impersonated service account ## PR Checklist - [x] Make sure you reviewed [CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md) - [x] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [x] Ensure the tests and linter pass - [x] Code coverage does not decrease (if any source code was changed) - [x] Appropriate docs were updated (if necessary) - [x] Make sure to add `!` if this involve a breaking change 🛠️ Fixes googleapis#2769 --------- Co-authored-by: kkeefer1 <kyle_keefer@intuit.com> Co-authored-by: Wenxin Du <117315983+duwenxin99@users.noreply.github.com> 9c3a748
github-actions bot
pushed a commit
to xaas-cloud/genai-toolbox
that referenced
this pull request
Mar 28, 2026
…ig (googleapis#2770) ## Summary Add `BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT` env var support to the prebuilt BigQuery configuration, enabling service account impersonation without requiring a custom `--tools-file`. ## Problem The BigQuery source already supports `impersonateServiceAccount` (added in googleapis#1641 / googleapis#906), but the prebuilt config at `internal/prebuiltconfigs/tools/bigquery.yaml` does not expose it via an environment variable. This forces users who need impersonation to abandon `--prebuilt bigquery` entirely and create a custom `--tools-file` that manually redefines all 9 tools — just to set one field on the source. This is a common need for organizations that use service account impersonation to scope permissions for AI agents, rather than granting broad access to individual user accounts. ## Solution Add a single line to the prebuilt BigQuery YAML: ```yaml impersonateServiceAccount: ${BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT:} ``` The empty default (`:`) means existing users are unaffected — the field is ignored when the env var is not set, preserving full backward compatibility. ## Validation Built the patched binary locally and confirmed: - Without the env var: `SESSION_USER()` returns the personal account (unchanged behavior) - With the env var: `SESSION_USER()` returns the impersonated service account ## PR Checklist - [x] Make sure you reviewed [CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md) - [x] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [x] Ensure the tests and linter pass - [x] Code coverage does not decrease (if any source code was changed) - [x] Appropriate docs were updated (if necessary) - [x] Make sure to add `!` if this involve a breaking change 🛠️ Fixes googleapis#2769 --------- Co-authored-by: kkeefer1 <kyle_keefer@intuit.com> Co-authored-by: Wenxin Du <117315983+duwenxin99@users.noreply.github.com> 9c3a748
github-actions bot
pushed a commit
to CrazyForks/genai-toolbox
that referenced
this pull request
Mar 28, 2026
…ig (googleapis#2770) ## Summary Add `BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT` env var support to the prebuilt BigQuery configuration, enabling service account impersonation without requiring a custom `--tools-file`. ## Problem The BigQuery source already supports `impersonateServiceAccount` (added in googleapis#1641 / googleapis#906), but the prebuilt config at `internal/prebuiltconfigs/tools/bigquery.yaml` does not expose it via an environment variable. This forces users who need impersonation to abandon `--prebuilt bigquery` entirely and create a custom `--tools-file` that manually redefines all 9 tools — just to set one field on the source. This is a common need for organizations that use service account impersonation to scope permissions for AI agents, rather than granting broad access to individual user accounts. ## Solution Add a single line to the prebuilt BigQuery YAML: ```yaml impersonateServiceAccount: ${BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT:} ``` The empty default (`:`) means existing users are unaffected — the field is ignored when the env var is not set, preserving full backward compatibility. ## Validation Built the patched binary locally and confirmed: - Without the env var: `SESSION_USER()` returns the personal account (unchanged behavior) - With the env var: `SESSION_USER()` returns the impersonated service account ## PR Checklist - [x] Make sure you reviewed [CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md) - [x] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [x] Ensure the tests and linter pass - [x] Code coverage does not decrease (if any source code was changed) - [x] Appropriate docs were updated (if necessary) - [x] Make sure to add `!` if this involve a breaking change 🛠️ Fixes googleapis#2769 --------- Co-authored-by: kkeefer1 <kyle_keefer@intuit.com> Co-authored-by: Wenxin Du <117315983+duwenxin99@users.noreply.github.com> 9c3a748
github-actions bot
pushed a commit
to CrazyForks/genai-toolbox
that referenced
this pull request
Mar 28, 2026
…ig (googleapis#2770) ## Summary Add `BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT` env var support to the prebuilt BigQuery configuration, enabling service account impersonation without requiring a custom `--tools-file`. ## Problem The BigQuery source already supports `impersonateServiceAccount` (added in googleapis#1641 / googleapis#906), but the prebuilt config at `internal/prebuiltconfigs/tools/bigquery.yaml` does not expose it via an environment variable. This forces users who need impersonation to abandon `--prebuilt bigquery` entirely and create a custom `--tools-file` that manually redefines all 9 tools — just to set one field on the source. This is a common need for organizations that use service account impersonation to scope permissions for AI agents, rather than granting broad access to individual user accounts. ## Solution Add a single line to the prebuilt BigQuery YAML: ```yaml impersonateServiceAccount: ${BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT:} ``` The empty default (`:`) means existing users are unaffected — the field is ignored when the env var is not set, preserving full backward compatibility. ## Validation Built the patched binary locally and confirmed: - Without the env var: `SESSION_USER()` returns the personal account (unchanged behavior) - With the env var: `SESSION_USER()` returns the impersonated service account ## PR Checklist - [x] Make sure you reviewed [CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md) - [x] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [x] Ensure the tests and linter pass - [x] Code coverage does not decrease (if any source code was changed) - [x] Appropriate docs were updated (if necessary) - [x] Make sure to add `!` if this involve a breaking change 🛠️ Fixes googleapis#2769 --------- Co-authored-by: kkeefer1 <kyle_keefer@intuit.com> Co-authored-by: Wenxin Du <117315983+duwenxin99@users.noreply.github.com> 9c3a748
github-actions bot
pushed a commit
to azaj01/genai-toolbox
that referenced
this pull request
Mar 29, 2026
…ig (googleapis#2770) ## Summary Add `BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT` env var support to the prebuilt BigQuery configuration, enabling service account impersonation without requiring a custom `--tools-file`. ## Problem The BigQuery source already supports `impersonateServiceAccount` (added in googleapis#1641 / googleapis#906), but the prebuilt config at `internal/prebuiltconfigs/tools/bigquery.yaml` does not expose it via an environment variable. This forces users who need impersonation to abandon `--prebuilt bigquery` entirely and create a custom `--tools-file` that manually redefines all 9 tools — just to set one field on the source. This is a common need for organizations that use service account impersonation to scope permissions for AI agents, rather than granting broad access to individual user accounts. ## Solution Add a single line to the prebuilt BigQuery YAML: ```yaml impersonateServiceAccount: ${BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT:} ``` The empty default (`:`) means existing users are unaffected — the field is ignored when the env var is not set, preserving full backward compatibility. ## Validation Built the patched binary locally and confirmed: - Without the env var: `SESSION_USER()` returns the personal account (unchanged behavior) - With the env var: `SESSION_USER()` returns the impersonated service account ## PR Checklist - [x] Make sure you reviewed [CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md) - [x] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [x] Ensure the tests and linter pass - [x] Code coverage does not decrease (if any source code was changed) - [x] Appropriate docs were updated (if necessary) - [x] Make sure to add `!` if this involve a breaking change 🛠️ Fixes googleapis#2769 --------- Co-authored-by: kkeefer1 <kyle_keefer@intuit.com> Co-authored-by: Wenxin Du <117315983+duwenxin99@users.noreply.github.com> 9c3a748
github-actions bot
pushed a commit
to azaj01/genai-toolbox
that referenced
this pull request
Mar 29, 2026
…ig (googleapis#2770) ## Summary Add `BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT` env var support to the prebuilt BigQuery configuration, enabling service account impersonation without requiring a custom `--tools-file`. ## Problem The BigQuery source already supports `impersonateServiceAccount` (added in googleapis#1641 / googleapis#906), but the prebuilt config at `internal/prebuiltconfigs/tools/bigquery.yaml` does not expose it via an environment variable. This forces users who need impersonation to abandon `--prebuilt bigquery` entirely and create a custom `--tools-file` that manually redefines all 9 tools — just to set one field on the source. This is a common need for organizations that use service account impersonation to scope permissions for AI agents, rather than granting broad access to individual user accounts. ## Solution Add a single line to the prebuilt BigQuery YAML: ```yaml impersonateServiceAccount: ${BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT:} ``` The empty default (`:`) means existing users are unaffected — the field is ignored when the env var is not set, preserving full backward compatibility. ## Validation Built the patched binary locally and confirmed: - Without the env var: `SESSION_USER()` returns the personal account (unchanged behavior) - With the env var: `SESSION_USER()` returns the impersonated service account ## PR Checklist - [x] Make sure you reviewed [CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md) - [x] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [x] Ensure the tests and linter pass - [x] Code coverage does not decrease (if any source code was changed) - [x] Appropriate docs were updated (if necessary) - [x] Make sure to add `!` if this involve a breaking change 🛠️ Fixes googleapis#2769 --------- Co-authored-by: kkeefer1 <kyle_keefer@intuit.com> Co-authored-by: Wenxin Du <117315983+duwenxin99@users.noreply.github.com> 9c3a748
github-actions bot
pushed a commit
to bhardwajRahul/genai-toolbox
that referenced
this pull request
Mar 29, 2026
…ig (googleapis#2770) ## Summary Add `BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT` env var support to the prebuilt BigQuery configuration, enabling service account impersonation without requiring a custom `--tools-file`. ## Problem The BigQuery source already supports `impersonateServiceAccount` (added in googleapis#1641 / googleapis#906), but the prebuilt config at `internal/prebuiltconfigs/tools/bigquery.yaml` does not expose it via an environment variable. This forces users who need impersonation to abandon `--prebuilt bigquery` entirely and create a custom `--tools-file` that manually redefines all 9 tools — just to set one field on the source. This is a common need for organizations that use service account impersonation to scope permissions for AI agents, rather than granting broad access to individual user accounts. ## Solution Add a single line to the prebuilt BigQuery YAML: ```yaml impersonateServiceAccount: ${BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT:} ``` The empty default (`:`) means existing users are unaffected — the field is ignored when the env var is not set, preserving full backward compatibility. ## Validation Built the patched binary locally and confirmed: - Without the env var: `SESSION_USER()` returns the personal account (unchanged behavior) - With the env var: `SESSION_USER()` returns the impersonated service account ## PR Checklist - [x] Make sure you reviewed [CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md) - [x] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [x] Ensure the tests and linter pass - [x] Code coverage does not decrease (if any source code was changed) - [x] Appropriate docs were updated (if necessary) - [x] Make sure to add `!` if this involve a breaking change 🛠️ Fixes googleapis#2769 --------- Co-authored-by: kkeefer1 <kyle_keefer@intuit.com> Co-authored-by: Wenxin Du <117315983+duwenxin99@users.noreply.github.com> 9c3a748
github-actions bot
pushed a commit
to bhardwajRahul/genai-toolbox
that referenced
this pull request
Mar 29, 2026
…ig (googleapis#2770) ## Summary Add `BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT` env var support to the prebuilt BigQuery configuration, enabling service account impersonation without requiring a custom `--tools-file`. ## Problem The BigQuery source already supports `impersonateServiceAccount` (added in googleapis#1641 / googleapis#906), but the prebuilt config at `internal/prebuiltconfigs/tools/bigquery.yaml` does not expose it via an environment variable. This forces users who need impersonation to abandon `--prebuilt bigquery` entirely and create a custom `--tools-file` that manually redefines all 9 tools — just to set one field on the source. This is a common need for organizations that use service account impersonation to scope permissions for AI agents, rather than granting broad access to individual user accounts. ## Solution Add a single line to the prebuilt BigQuery YAML: ```yaml impersonateServiceAccount: ${BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT:} ``` The empty default (`:`) means existing users are unaffected — the field is ignored when the env var is not set, preserving full backward compatibility. ## Validation Built the patched binary locally and confirmed: - Without the env var: `SESSION_USER()` returns the personal account (unchanged behavior) - With the env var: `SESSION_USER()` returns the impersonated service account ## PR Checklist - [x] Make sure you reviewed [CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md) - [x] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [x] Ensure the tests and linter pass - [x] Code coverage does not decrease (if any source code was changed) - [x] Appropriate docs were updated (if necessary) - [x] Make sure to add `!` if this involve a breaking change 🛠️ Fixes googleapis#2769 --------- Co-authored-by: kkeefer1 <kyle_keefer@intuit.com> Co-authored-by: Wenxin Du <117315983+duwenxin99@users.noreply.github.com> 9c3a748
github-actions bot
pushed a commit
to NirajNandre/genai-toolbox-fork
that referenced
this pull request
Mar 29, 2026
…ig (googleapis#2770) ## Summary Add `BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT` env var support to the prebuilt BigQuery configuration, enabling service account impersonation without requiring a custom `--tools-file`. ## Problem The BigQuery source already supports `impersonateServiceAccount` (added in googleapis#1641 / googleapis#906), but the prebuilt config at `internal/prebuiltconfigs/tools/bigquery.yaml` does not expose it via an environment variable. This forces users who need impersonation to abandon `--prebuilt bigquery` entirely and create a custom `--tools-file` that manually redefines all 9 tools — just to set one field on the source. This is a common need for organizations that use service account impersonation to scope permissions for AI agents, rather than granting broad access to individual user accounts. ## Solution Add a single line to the prebuilt BigQuery YAML: ```yaml impersonateServiceAccount: ${BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT:} ``` The empty default (`:`) means existing users are unaffected — the field is ignored when the env var is not set, preserving full backward compatibility. ## Validation Built the patched binary locally and confirmed: - Without the env var: `SESSION_USER()` returns the personal account (unchanged behavior) - With the env var: `SESSION_USER()` returns the impersonated service account ## PR Checklist - [x] Make sure you reviewed [CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md) - [x] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [x] Ensure the tests and linter pass - [x] Code coverage does not decrease (if any source code was changed) - [x] Appropriate docs were updated (if necessary) - [x] Make sure to add `!` if this involve a breaking change 🛠️ Fixes googleapis#2769 --------- Co-authored-by: kkeefer1 <kyle_keefer@intuit.com> Co-authored-by: Wenxin Du <117315983+duwenxin99@users.noreply.github.com> 9c3a748
github-actions bot
pushed a commit
to NirajNandre/genai-toolbox-fork
that referenced
this pull request
Mar 29, 2026
…ig (googleapis#2770) ## Summary Add `BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT` env var support to the prebuilt BigQuery configuration, enabling service account impersonation without requiring a custom `--tools-file`. ## Problem The BigQuery source already supports `impersonateServiceAccount` (added in googleapis#1641 / googleapis#906), but the prebuilt config at `internal/prebuiltconfigs/tools/bigquery.yaml` does not expose it via an environment variable. This forces users who need impersonation to abandon `--prebuilt bigquery` entirely and create a custom `--tools-file` that manually redefines all 9 tools — just to set one field on the source. This is a common need for organizations that use service account impersonation to scope permissions for AI agents, rather than granting broad access to individual user accounts. ## Solution Add a single line to the prebuilt BigQuery YAML: ```yaml impersonateServiceAccount: ${BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT:} ``` The empty default (`:`) means existing users are unaffected — the field is ignored when the env var is not set, preserving full backward compatibility. ## Validation Built the patched binary locally and confirmed: - Without the env var: `SESSION_USER()` returns the personal account (unchanged behavior) - With the env var: `SESSION_USER()` returns the impersonated service account ## PR Checklist - [x] Make sure you reviewed [CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md) - [x] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [x] Ensure the tests and linter pass - [x] Code coverage does not decrease (if any source code was changed) - [x] Appropriate docs were updated (if necessary) - [x] Make sure to add `!` if this involve a breaking change 🛠️ Fixes googleapis#2769 --------- Co-authored-by: kkeefer1 <kyle_keefer@intuit.com> Co-authored-by: Wenxin Du <117315983+duwenxin99@users.noreply.github.com> 9c3a748
github-actions bot
pushed a commit
to TheTechOddBug/genai-toolbox
that referenced
this pull request
Mar 29, 2026
…ig (googleapis#2770) ## Summary Add `BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT` env var support to the prebuilt BigQuery configuration, enabling service account impersonation without requiring a custom `--tools-file`. ## Problem The BigQuery source already supports `impersonateServiceAccount` (added in googleapis#1641 / googleapis#906), but the prebuilt config at `internal/prebuiltconfigs/tools/bigquery.yaml` does not expose it via an environment variable. This forces users who need impersonation to abandon `--prebuilt bigquery` entirely and create a custom `--tools-file` that manually redefines all 9 tools — just to set one field on the source. This is a common need for organizations that use service account impersonation to scope permissions for AI agents, rather than granting broad access to individual user accounts. ## Solution Add a single line to the prebuilt BigQuery YAML: ```yaml impersonateServiceAccount: ${BIGQUERY_IMPERSONATE_SERVICE_ACCOUNT:} ``` The empty default (`:`) means existing users are unaffected — the field is ignored when the env var is not set, preserving full backward compatibility. ## Validation Built the patched binary locally and confirmed: - Without the env var: `SESSION_USER()` returns the personal account (unchanged behavior) - With the env var: `SESSION_USER()` returns the impersonated service account ## PR Checklist - [x] Make sure you reviewed [CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md) - [x] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [x] Ensure the tests and linter pass - [x] Code coverage does not decrease (if any source code was changed) - [x] Appropriate docs were updated (if necessary) - [x] Make sure to add `!` if this involve a breaking change 🛠️ Fixes googleapis#2769 --------- Co-authored-by: kkeefer1 <kyle_keefer@intuit.com> Co-authored-by: Wenxin Du <117315983+duwenxin99@users.noreply.github.com> 9c3a748
Yuan325
added a commit
that referenced
this pull request
Apr 8, 2026
🤖 I have created a release *beep* *boop* --- ## [0.32.0](v0.31.0...v0.32.0) (2026-04-08) ### ⚠ BREAKING CHANGES * update repo name ([#2968](#2968)) ### Features * Add MCP tool annotations to all remaining tools ([#2221](#2221)) ([ea09db9](ea09db9)) * **bigquery:** Add conversational analytics tools for Data Agents ([#2517](#2517)) ([2490a4b](2490a4b)) * **embeddingModel:** Add Backend API selection fields ([#2592](#2592)) ([912aa9e](912aa9e)) * **skills:** Add Claude Code support to generated scripts ([#2966](#2966)) ([a1609e1](a1609e1)) * **skills:** Add codex user agent ([#2973](#2973)) ([070e939](070e939)) * **skills:** Tool invocation via npx ([#2916](#2916)) ([377dc5b](377dc5b)) * **sources/singlestore:** Add ConnectionParams to SingleStore Config ([#2555](#2555)) ([73e2a8c](73e2a8c)) * **tool/dataplex-lookup-context:** Relax project constraint and enforce location ([#2952](#2952)) ([7ebfdf1](7ebfdf1)) * **tools/looker:** Looker agent management from MCP ([#2830](#2830)) ([649d4ad](649d4ad)) * **ui:** Update to use `/mcp` endpoint ([#2829](#2829)) ([c3059c2](c3059c2)) ### Bug Fixes * **bigquery:** Add impersonateServiceAccount to prebuilt config ([#2770](#2770)) ([9c3a748](9c3a748)) * **quickstart:** Robust tool lookup and modernize dependencies in Python samples ([#2863](#2863)) ([4c0845d](4c0845d)) * **skills:** Fix skill generation template ([#2914](#2914)) ([a01a15e](a01a15e)) * **skills:** Prevent empty strings overriding optional env vars in node scripts ([#2963](#2963)) ([c52adeb](c52adeb)) * **tests/bigquery:** Implement uuid-based isolation and reliable resource cleanup ([#2547](#2547)) ([479d842](479d842)) * **tests/Bigtable:** Implement uuid-based isolation and reliable resource cleanup ([#2880](#2880)) ([a769f15](a769f15)) * Update error for ConvertConfig function ([#2993](#2993)) ([62bdabb](62bdabb)) ### Code Refactoring * Update repo name ([#2968](#2968)) ([3aae809](3aae809)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). --------- Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com> Co-authored-by: Yuan Teoh <45984206+Yuan325@users.noreply.github.com>
github-actions bot
pushed a commit
that referenced
this pull request
Apr 8, 2026
🤖 I have created a release *beep* *boop* --- ## [0.32.0](v0.31.0...v0.32.0) (2026-04-08) ### ⚠ BREAKING CHANGES * update repo name ([#2968](#2968)) ### Features * Add MCP tool annotations to all remaining tools ([#2221](#2221)) ([ea09db9](ea09db9)) * **bigquery:** Add conversational analytics tools for Data Agents ([#2517](#2517)) ([2490a4b](2490a4b)) * **embeddingModel:** Add Backend API selection fields ([#2592](#2592)) ([912aa9e](912aa9e)) * **skills:** Add Claude Code support to generated scripts ([#2966](#2966)) ([a1609e1](a1609e1)) * **skills:** Add codex user agent ([#2973](#2973)) ([070e939](070e939)) * **skills:** Tool invocation via npx ([#2916](#2916)) ([377dc5b](377dc5b)) * **sources/singlestore:** Add ConnectionParams to SingleStore Config ([#2555](#2555)) ([73e2a8c](73e2a8c)) * **tool/dataplex-lookup-context:** Relax project constraint and enforce location ([#2952](#2952)) ([7ebfdf1](7ebfdf1)) * **tools/looker:** Looker agent management from MCP ([#2830](#2830)) ([649d4ad](649d4ad)) * **ui:** Update to use `/mcp` endpoint ([#2829](#2829)) ([c3059c2](c3059c2)) ### Bug Fixes * **bigquery:** Add impersonateServiceAccount to prebuilt config ([#2770](#2770)) ([9c3a748](9c3a748)) * **quickstart:** Robust tool lookup and modernize dependencies in Python samples ([#2863](#2863)) ([4c0845d](4c0845d)) * **skills:** Fix skill generation template ([#2914](#2914)) ([a01a15e](a01a15e)) * **skills:** Prevent empty strings overriding optional env vars in node scripts ([#2963](#2963)) ([c52adeb](c52adeb)) * **tests/bigquery:** Implement uuid-based isolation and reliable resource cleanup ([#2547](#2547)) ([479d842](479d842)) * **tests/Bigtable:** Implement uuid-based isolation and reliable resource cleanup ([#2880](#2880)) ([a769f15](a769f15)) * Update error for ConvertConfig function ([#2993](#2993)) ([62bdabb](62bdabb)) ### Code Refactoring * Update repo name ([#2968](#2968)) ([3aae809](3aae809)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). --------- Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com> Co-authored-by: Yuan Teoh <45984206+Yuan325@users.noreply.github.com> b9ae1c6
github-actions bot
pushed a commit
to renovate-bot/googleapis-_-genai-toolbox
that referenced
this pull request
Apr 8, 2026
🤖 I have created a release *beep* *boop* --- ## [0.32.0](googleapis/mcp-toolbox@v0.31.0...v0.32.0) (2026-04-08) ### ⚠ BREAKING CHANGES * update repo name ([googleapis#2968](googleapis#2968)) ### Features * Add MCP tool annotations to all remaining tools ([googleapis#2221](googleapis#2221)) ([ea09db9](googleapis@ea09db9)) * **bigquery:** Add conversational analytics tools for Data Agents ([googleapis#2517](googleapis#2517)) ([2490a4b](googleapis@2490a4b)) * **embeddingModel:** Add Backend API selection fields ([googleapis#2592](googleapis#2592)) ([912aa9e](googleapis@912aa9e)) * **skills:** Add Claude Code support to generated scripts ([googleapis#2966](googleapis#2966)) ([a1609e1](googleapis@a1609e1)) * **skills:** Add codex user agent ([googleapis#2973](googleapis#2973)) ([070e939](googleapis@070e939)) * **skills:** Tool invocation via npx ([googleapis#2916](googleapis#2916)) ([377dc5b](googleapis@377dc5b)) * **sources/singlestore:** Add ConnectionParams to SingleStore Config ([googleapis#2555](googleapis#2555)) ([73e2a8c](googleapis@73e2a8c)) * **tool/dataplex-lookup-context:** Relax project constraint and enforce location ([googleapis#2952](googleapis#2952)) ([7ebfdf1](googleapis@7ebfdf1)) * **tools/looker:** Looker agent management from MCP ([googleapis#2830](googleapis#2830)) ([649d4ad](googleapis@649d4ad)) * **ui:** Update to use `/mcp` endpoint ([googleapis#2829](googleapis#2829)) ([c3059c2](googleapis@c3059c2)) ### Bug Fixes * **bigquery:** Add impersonateServiceAccount to prebuilt config ([googleapis#2770](googleapis#2770)) ([9c3a748](googleapis@9c3a748)) * **quickstart:** Robust tool lookup and modernize dependencies in Python samples ([googleapis#2863](googleapis#2863)) ([4c0845d](googleapis@4c0845d)) * **skills:** Fix skill generation template ([googleapis#2914](googleapis#2914)) ([a01a15e](googleapis@a01a15e)) * **skills:** Prevent empty strings overriding optional env vars in node scripts ([googleapis#2963](googleapis#2963)) ([c52adeb](googleapis@c52adeb)) * **tests/bigquery:** Implement uuid-based isolation and reliable resource cleanup ([googleapis#2547](googleapis#2547)) ([479d842](googleapis@479d842)) * **tests/Bigtable:** Implement uuid-based isolation and reliable resource cleanup ([googleapis#2880](googleapis#2880)) ([a769f15](googleapis@a769f15)) * Update error for ConvertConfig function ([googleapis#2993](googleapis#2993)) ([62bdabb](googleapis@62bdabb)) ### Code Refactoring * Update repo name ([googleapis#2968](googleapis#2968)) ([3aae809](googleapis@3aae809)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). --------- Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com> Co-authored-by: Yuan Teoh <45984206+Yuan325@users.noreply.github.com> b9ae1c6
github-actions bot
pushed a commit
to Jaleel-zhu/genai-toolbox
that referenced
this pull request
Apr 8, 2026
🤖 I have created a release *beep* *boop* --- ## [0.32.0](googleapis/mcp-toolbox@v0.31.0...v0.32.0) (2026-04-08) ### ⚠ BREAKING CHANGES * update repo name ([googleapis#2968](googleapis#2968)) ### Features * Add MCP tool annotations to all remaining tools ([googleapis#2221](googleapis#2221)) ([ea09db9](googleapis@ea09db9)) * **bigquery:** Add conversational analytics tools for Data Agents ([googleapis#2517](googleapis#2517)) ([2490a4b](googleapis@2490a4b)) * **embeddingModel:** Add Backend API selection fields ([googleapis#2592](googleapis#2592)) ([912aa9e](googleapis@912aa9e)) * **skills:** Add Claude Code support to generated scripts ([googleapis#2966](googleapis#2966)) ([a1609e1](googleapis@a1609e1)) * **skills:** Add codex user agent ([googleapis#2973](googleapis#2973)) ([070e939](googleapis@070e939)) * **skills:** Tool invocation via npx ([googleapis#2916](googleapis#2916)) ([377dc5b](googleapis@377dc5b)) * **sources/singlestore:** Add ConnectionParams to SingleStore Config ([googleapis#2555](googleapis#2555)) ([73e2a8c](googleapis@73e2a8c)) * **tool/dataplex-lookup-context:** Relax project constraint and enforce location ([googleapis#2952](googleapis#2952)) ([7ebfdf1](googleapis@7ebfdf1)) * **tools/looker:** Looker agent management from MCP ([googleapis#2830](googleapis#2830)) ([649d4ad](googleapis@649d4ad)) * **ui:** Update to use `/mcp` endpoint ([googleapis#2829](googleapis#2829)) ([c3059c2](googleapis@c3059c2)) ### Bug Fixes * **bigquery:** Add impersonateServiceAccount to prebuilt config ([googleapis#2770](googleapis#2770)) ([9c3a748](googleapis@9c3a748)) * **quickstart:** Robust tool lookup and modernize dependencies in Python samples ([googleapis#2863](googleapis#2863)) ([4c0845d](googleapis@4c0845d)) * **skills:** Fix skill generation template ([googleapis#2914](googleapis#2914)) ([a01a15e](googleapis@a01a15e)) * **skills:** Prevent empty strings overriding optional env vars in node scripts ([googleapis#2963](googleapis#2963)) ([c52adeb](googleapis@c52adeb)) * **tests/bigquery:** Implement uuid-based isolation and reliable resource cleanup ([googleapis#2547](googleapis#2547)) ([479d842](googleapis@479d842)) * **tests/Bigtable:** Implement uuid-based isolation and reliable resource cleanup ([googleapis#2880](googleapis#2880)) ([a769f15](googleapis@a769f15)) * Update error for ConvertConfig function ([googleapis#2993](googleapis#2993)) ([62bdabb](googleapis@62bdabb)) ### Code Refactoring * Update repo name ([googleapis#2968](googleapis#2968)) ([3aae809](googleapis@3aae809)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). --------- Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com> Co-authored-by: Yuan Teoh <45984206+Yuan325@users.noreply.github.com> b9ae1c6
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add
BIGQUERY_IMPERSONATE_SERVICE_ACCOUNTenv var support to the prebuilt BigQuery configuration, enabling service account impersonation without requiring a custom--tools-file.Problem
The BigQuery source already supports
impersonateServiceAccount(added in #1641 / #906), but the prebuilt config atinternal/prebuiltconfigs/tools/bigquery.yamldoes not expose it via an environment variable. This forces users who need impersonation to abandon--prebuilt bigqueryentirely and create a custom--tools-filethat manually redefines all 9 tools — just to set one field on the source.This is a common need for organizations that use service account impersonation to scope permissions for AI agents, rather than granting broad access to individual user accounts.
Solution
Add a single line to the prebuilt BigQuery YAML:
The empty default (
:) means existing users are unaffected — the field is ignored when the env var is not set, preserving full backward compatibility.Validation
Built the patched binary locally and confirmed:
SESSION_USER()returns the personal account (unchanged behavior)SESSION_USER()returns the impersonated service accountPR Checklist
!if this involve a breaking change🛠️ Fixes #2769