Disable Version Secrets

secret_manager.disable_version_secrets
ActionGoogle Cloudconnection required

Calls secretmanager v1 POST /v1/projects/{projectsId}/secrets/{secretsId}/versions/{versionsId}:disable.

Disables a SecretVersion.

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, 3 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
secret
Secret name or id.
stringYes———
version
Version name or id.
stringYes———
body
The DisableSecretVersionRequest resource, as the API defines it.
objectYes———

Output

One shape.

result

Extra keys beyond the ones listed can appear.

FieldTypeExample
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": ""
}

See Disable Version Secrets 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.