Rotate Secret Secret
secret_manager.rotate_secret_secret
ActionGoogle Cloudconnection required
Calls secretmanager v1 POST /v1/projects/{projectsId}/locations/{locationsId}/secrets/{secretsId}:rotateSecret.
Do a managed rotation for a Secret.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google Secret Manager
- Secret shape
- {"client_id", "client_secret", "refresh_token"}
- Config it needs
- project_id
- Resolved by
- config.connection_id, else node.connection_id
Configuration
3 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
location Location or region; taken from the connection when unset. | string | No | — | — | — |
secret Secret name or id. | string | Yes | — | — | — |
body The RotateSecretRequest resource, as the API defines it. | object | Yes | — | — | — |
Output
One shape.
result
Extra keys beyond the ones listed can appear.
| Field | Type | Example |
|---|---|---|
clientSpecifiedPayloadChecksum | boolean | — |
createTime | string | — |
customerManagedEncryption | object | — |
destroyTime | string | — |
etag | string | — |
name | string | — |
replicationStatus | object | — |
scheduledDestroyTime | string | — |
state | string | — |
{
"clientSpecifiedPayloadChecksum": false,
"createTime": "",
"customerManagedEncryption": {},
"destroyTime": "",
"etag": "",
"name": "",
"replicationStatus": {},
"scheduledDestroyTime": "",
"state": ""
}Related Google Secret Manager nodes
See Rotate Secret Secret run in a workflow.
In a technical demo we add the Google Secret Manager connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.