Export Trusted Key Wrapped Crypto Key Version Crypto Key Version

cloud_kms.export_trusted_key_wrapped_crypto_key_version_crypto_key_version
ActionGoogle Cloudconnection required

Calls cloudkms v1 GET /v1/projects/{projectsId}/locations/{locationsId}/keyRings/{keyRingsId}/cryptoKeys/{cryptoKeysId}/cryptoKeyVersions/{cryptoKeyVersionsId}:exportTrustedKeyWrappedCryptoKeyVersion.

Exports a CryptoKeyVersion with a trusted key.

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, 4 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———
crypto_key_version
Crypto key version name or id.
stringYes———
wrapping_key
The name of the CryptoKeyVersion to use as a wrapping key. Required.
stringYes———

Output

One shape.

result

Extra keys beyond the ones listed can appear.

FieldTypeExample
wrappedKey
string—
wrappedKeyCrc32c
string—
{
  "wrappedKey": "",
  "wrappedKeyCrc32c": ""
}

See Export Trusted Key Wrapped Crypto Key Version Crypto Key Version 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.