Google Cloud
Google Cloud is the primary cloud provider with dedicated integration support in the current codebase. The registry supports `gcp`, the alias `google-cloud`, and a separate `google-logs` provider for logging-oriented flows.
Purpose
Configure Google Cloud access through the authenticated integration routes. Then use Environment monitoring, secret storage, and usage-ingestion features in the product.
Prerequisites
- A signed-in Supabase session.
- A CSRF token for POST and PATCH requests.
- A Google Cloud service account key JSON when using the current settings UI flow.
Setup
1
Create the credential with POST /api/integrations using provider `gcp` and a `service_account_key` payload when you use the current UI.
2
Use Integrations settings to attach the credential to an Environment.
3
Configure Environment log scanning with /api/projects/[projectId]/log-scanning/configs for Cloud Run or Cloud Logging ingestion.
API & contracts
| Field | Type | Description |
|---|---|---|
| gcp | api_key | The alias map resolves `google-cloud` to `gcp`. |
| google-logs | api_key | This provider is used for logging-specific workflows and the settings UI can fall back to the main `gcp` credential. |
- The GCP verifier parses `service_account_key` and attempts to verify service-account credentials.
- Environment connector bindings accept `gcp` and `google-logs` connector types.
- The agentic connector registry has dedicated connector implementations for `gcp` and `google-logs` rather than the generic API-key path.
Failure modes
- POST /api/integrations returns 400 for unsupported auth types or invalid request payloads.
- GCP verification fails when the supplied service account key cannot be parsed or authenticated.
- Mutation routes return 401 without a session and 403 when the CSRF token is missing.