Update Ekm Config Location
cloud_kms.update_ekm_config_location
ActionGoogle Cloudconnection required
Calls cloudkms v1 PATCH /v1/projects/{projectsId}/locations/{locationsId}/ekmConfig.
Updates the EkmConfig singleton resource for a given project and location.
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
3 fields, 1 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 | — | — | — |
body The EkmConfig resource, as the API defines it. | object | Yes | — | — | — |
update_mask List of fields to be updated in this request. Optional. | string | No | — | — | — |
Output
One shape.
result
Extra keys beyond the ones listed can appear.
| Field | Type | Example |
|---|---|---|
defaultEkmConnection | string | — |
name | string | — |
{
"defaultEkmConnection": "",
"name": ""
}See Update Ekm Config Location 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.