Create Managed Zone
cloud_dns.create_managed_zone
ActionGoogle Cloudconnection required
Calls dns v1 POST /dns/v1/projects/{project}/managedZones.
Creates a new 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
1 field, 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 |
|---|---|---|---|---|---|
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 |
|---|---|---|
cloudLoggingConfig | object | — |
creationTime | string | — |
description | string | — |
dnsName | string | — |
dnssecConfig | object | — |
forwardingConfig | object | — |
id | string | — |
kind | string | — |
labels | object | — |
name | string | — |
nameServerSet | string | — |
nameServers | array | — |
peeringConfig | object | — |
privateVisibilityConfig | object | — |
reverseLookupConfig | object | — |
serviceDirectoryConfig | object | — |
visibility | string | — |
{
"cloudLoggingConfig": {},
"creationTime": "",
"description": "",
"dnsName": "",
"dnssecConfig": {},
"forwardingConfig": {},
"id": "",
"kind": "",
"labels": {},
"name": "",
"nameServerSet": "",
"nameServers": [],
"peeringConfig": {},
"privateVisibilityConfig": {},
"reverseLookupConfig": {},
"serviceDirectoryConfig": {},
"visibility": ""
}See Create 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.