Update Managed Zone

cloud_dns.update_managed_zone
ActionGoogle Cloudconnection required

Calls dns v1 PATCH /dns/v1/projects/{project}/managedZones/{managedZone}.

Applies a partial update to an existing ManagedZone.

Connection

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

Configuration

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

FieldTypeRequiredDefaultConstraintsExample
managed_zone
Managed zone name or id.
stringYes———
body
The ManagedZone resource, as the API defines it.
objectYes———

Output

One shape.

result

Extra keys beyond the ones listed can appear.

FieldTypeExample
dnsKeyContext
object—
id
string—
kind
string—
startTime
string—
status
string—
type
string—
user
string—
zoneContext
object—
{
  "dnsKeyContext": {},
  "id": "",
  "kind": "",
  "startTime": "",
  "status": "",
  "type": "",
  "user": "",
  "zoneContext": {}
}

See Update Managed Zone run in a workflow.

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