Google Cloud Storage
Register a GCS bucket with a service-account key, or keylessly via Workload Identity.
Register a GCS bucket as a storage connection. Authenticate with a service-account JSON key, or - on GKE - keylessly via Workload Identity.
Register
eddytor create storage gcs \
--bucket mdm-prod \
--service-account-key-file ./eddytor-gcs-key.jsonAdd --discover-files to also register standalone Parquet/CSV as read-only
tables.
POST /v1/storages/gcs
Authorization: Bearer edd_live_…
{ "bucket_name": "mdm-prod",
"service_account_key": "{\"type\":\"service_account\", …}" }register_gcs_storage(bucket_name="mdm-prod",
service_account_key="{\"type\":\"service_account\", ...}")Pass the full service-account JSON as a string (or an OAuth token).
The bucket name becomes the config name. Registration probes the bucket, then discovers tables - see How registration works.
Keyless on GKE (Workload Identity)
Preferred over a mounted key: bind the Eddytor Kubernetes service account to a GCP
service account with roles/storage.objectAdmin on the bucket, and the pod gets
credentials ambiently - no key file. Setup is in
GKE / EKS.