Skip to content

Commit a79d101

Browse files
spicyfalafelclaude
andcommitted
docs: remove misleading External Secrets link — vault not supported by BigQuery module
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1 parent b334010 commit a79d101

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

docs/tutorials/subscriptions-tutorials/bigquery-aidboxtopicdestination.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -153,8 +153,8 @@ The module supports three authentication methods:
153153
2. **Application Default Credentials (ADC)** — omit `serviceAccountKey`. The module automatically uses the attached service account credentials. Recommended for Cloud Run and GKE with Workload Identity.
154154
3. **Emulator mode** — set `emulatorUrl` and `emulatorGrpcHost`. No authentication required.
155155

156-
{% hint style="warning" %}
157-
Avoid hardcoding the Service Account JSON key directly in resource definitions. Prefer **Application Default Credentials** (ADC) when running on Cloud Run or GKE — no key needed at all. For other environments, see [External Secrets](../../configuration/secret-files.md) to store the key in a vault config file instead of in the resource.
156+
{% hint style="info" %}
157+
On GCP (Cloud Run, GKE) you don't need a Service Account key — omit `serviceAccountKey` and the module will use Application Default Credentials automatically.
158158
{% endhint %}
159159

160160
### Required IAM Roles

0 commit comments

Comments
 (0)