GCP Self-Host: App-wiring for storage and vault (#6632)

Co-authored-by: Aaron Perez <aperez0295@gmail.com>
This commit is contained in:
Shuchang Zheng 2026-06-16 13:48:17 -07:00 committed by GitHub
parent cb6854bc5c
commit 209d715a4a
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
11 changed files with 137 additions and 12 deletions

View file

@ -179,3 +179,27 @@ SKYVERN_AUTH_BITWARDEN_CLIENT_SECRET=your-client-secret-here
# Optional: override Redis URL specifically for notifications (falls back to REDIS_URL)
# NOTIFICATION_REDIS_URL=
# REDIS_URL=redis://localhost:6379/0
# =============================================================================
# OPTIONAL: GCP SELF-HOSTED DEPLOYMENT
# =============================================================================
# Uncomment to run Skyvern on Google Cloud with GCS storage and Secret Manager
# credentials. Auth uses Application Default Credentials (Workload Identity on
# GKE, or GOOGLE_APPLICATION_CREDENTIALS pointing at a service-account key).
# Store artifacts/screenshots/browser sessions/uploads in Google Cloud Storage
# SKYVERN_STORAGE_TYPE=gcs
# GCS_PROJECT_ID=your-gcp-project-id
# GCS_BUCKET_ARTIFACTS=skyvern-artifacts
# GCS_BUCKET_SCREENSHOTS=skyvern-screenshots
# GCS_BUCKET_BROWSER_SESSIONS=skyvern-browser-sessions
# GCS_BUCKET_UPLOADS=skyvern-uploads
# Service account that signs GCS download URLs; required only under Workload
# Identity, where the runtime SA has no signing key of its own.
# GCS_SIGNER_SA_EMAIL=skyvern@your-gcp-project-id.iam.gserviceaccount.com
# Store workflow credentials in GCP Secret Manager instead of Bitwarden
# CREDENTIAL_VAULT_TYPE=gcp
# GCP_CREDENTIAL_VAULT_PROJECT_ID=your-gcp-project-id
# Secret-id prefix; must be unique per Skyvern deployment sharing a project
# GCP_CREDENTIAL_VAULT_PREFIX=skyvern-cred-