Update Secret Projects

secret_manager.update_secret_projects
ActionGoogle Cloudconnection required

Calls secretmanager v1 PATCH /v1/projects/{projectsId}/secrets/{secretsId}.

Updates metadata of an existing 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.

FieldTypeRequiredDefaultConstraintsExample
secret
Secret name or id.
stringYes———
body
The Secret resource, as the API defines it.
objectYes———
update_mask
Specifies the fields to be updated. Optional.
stringNo———

Output

One shape.

result

Extra keys beyond the ones listed can appear.

FieldTypeExample
annotations
object—
createTime
string—
customerManagedEncryption
object—
etag
string—
expireTime
string—
labels
object—
name
string—
policyMember
object—
replication
object—
rotation
object—
secretType
string—
tags
object—
topics
array—
ttl
string—
versionAliases
object—
versionDestroyTtl
string—
{
  "annotations": {},
  "createTime": "",
  "customerManagedEncryption": {},
  "etag": "",
  "expireTime": "",
  "labels": {},
  "name": "",
  "policyMember": {},
  "replication": {},
  "rotation": {},
  "secretType": "",
  "tags": {},
  "topics": [],
  "ttl": "",
  "versionAliases": {},
  "versionDestroyTtl": ""
}

See Update Secret Projects 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.