Rotate the stored credentials of a Google Cloud Storage configuration
The bucket is preserved; only the service-account key (+ optional expiry) moves. Delegated-OAuth configs answer 422 — see the provider link flow. **Required scope:** `storage:configure` (+ `storage_configs:share` for workspace-shared configs)
Authorization
BearerAuth Security scheme for OpenAPI endpoints. Validates both JWT tokens and API keys.
In: header
Path Parameters
uuidRequest Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Rotate the stored credential of a GCS config (ED-549). The bucket is
preserved from the existing configuration. See
[RotateS3CredentialsRequest] for what rotation deliberately cannot do.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
curl -X PUT "https://example.com/v1/storages/configs/497f6eca-6276-4993-bfeb-53cbbbba6f08/credentials/gcs" \ -H "Content-Type: application/json" \ -d '{ "serviceAccountKey": "string" }'{ "configId": "46ff6d11-d8b2-40d8-9197-dfa33c61cd6c", "configName": "string", "message": "string"}{ "code": "string", "message": "string", "request_id": "string", "details": [ { "field": "string", "message": "string" } ]}{ "code": "string", "message": "string", "request_id": "string", "details": [ { "field": "string", "message": "string" } ]}{ "code": "string", "message": "string", "request_id": "string", "details": [ { "field": "string", "message": "string" } ]}{ "code": "string", "message": "string", "request_id": "string", "details": [ { "field": "string", "message": "string" } ]}{ "code": "string", "message": "string", "request_id": "string", "details": [ { "field": "string", "message": "string" } ]}{ "code": "string", "message": "string", "request_id": "string", "details": [ { "field": "string", "message": "string" } ]}{ "code": "string", "message": "string", "request_id": "string", "details": [ { "field": "string", "message": "string" } ]}{ "code": "string", "message": "string", "request_id": "string", "details": [ { "field": "string", "message": "string" } ]}{ "code": "string", "message": "string", "request_id": "string", "details": [ { "field": "string", "message": "string" } ]}Rotate the stored credentials of an Azure storage configuration
Exactly one auth mode (access key, SAS token, service principal, or managed identity); account, container and endpoint flags are preserved. Delegated-OAuth configs hold no stored secret and answer 422 — update access there through the provider link flow. **Required scope:** `storage:configure` (+ `storage_configs:share` for workspace-shared configs)
Attach a storage configuration to a workspace
Two cases (ED-544): - **Personal config the caller owns** → promoted to workspace ownership. The promoter can undo within a short window (see the undo endpoint). - **Workspace-owned config** → re-attached to the target workspace. Requires Admin/Builder access to BOTH the current and the target workspace, and extinguishes any pending promote-undo window. The config id is stable in both cases, so its `cfg_{id}` catalog schema and every registered table keep resolving. Gaining access is additive — new members pick the config up on their next discovery refresh. *Losing* it is not: a re-attach drops the source workspace members' engine sessions so the config stops resolving for them immediately. Attaching to the default workspace is a deliberate org-wide share. **Required scope:** `storage_configs:share` (plus Admin or Builder access to the workspace(s) involved)