Update Crypto Key

cloud_kms.update_crypto_key
ActionGoogle Cloudconnection required

Calls cloudkms v1 PATCH /v1/projects/{projectsId}/locations/{locationsId}/keyRings/{keyRingsId}/cryptoKeys/{cryptoKeysId}.

Update a CryptoKey.

Connection

Required
Yes — the node will not save without one
Auth type
OAuth 2.0
Providers
Google Cloud KMS
Secret shape
{"client_id", "client_secret", "refresh_token"}
Config it needs
project_id, location, key_ring
Resolved by
config.connection_id, else node.connection_id

Configuration

5 fields, 3 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
location
Location or region; taken from the connection when unset.
stringNo———
key_ring
Key ring name or id.
stringYes———
crypto_key
Crypto key name or id.
stringYes———
body
The CryptoKey resource, as the API defines it.
objectYes———
update_mask
List of fields to be updated in this request. Optional.
stringNo———

Output

One shape.

result

Extra keys beyond the ones listed can appear.

FieldTypeExample
createTime
string—
cryptoKeyBackend
string—
destroyScheduledDuration
string—
importOnly
boolean—
keyAccessJustificationsPolicy
object—
labels
object—
name
string—
nextRotationTime
string—
primary
object—
purpose
string—
rotationPeriod
string—
versionTemplate
object—
{
  "createTime": "",
  "cryptoKeyBackend": "",
  "destroyScheduledDuration": "",
  "importOnly": false,
  "keyAccessJustificationsPolicy": {},
  "labels": {},
  "name": "",
  "nextRotationTime": "",
  "primary": {},
  "purpose": "",
  "rotationPeriod": "",
  "versionTemplate": {}
}

See Update Crypto Key run in a workflow.

In a technical demo we add the Google Cloud KMS connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.