Replace Managed Zone
cloud_dns.replace_managed_zone
ActionGoogle Cloudconnection required
Calls dns v1 PUT /dns/v1/projects/{project}/managedZones/{managedZone}.
Updates 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.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
managed_zone Managed zone name or id. | string | Yes | — | — | — |
body The ManagedZone resource, as the API defines it. | object | Yes | — | — | — |
Output
One shape.
result
Extra keys beyond the ones listed can appear.
| Field | Type | Example |
|---|---|---|
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 Replace 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.