Replace Response Policy Rule
cloud_dns.replace_response_policy_rule
ActionGoogle Cloudconnection required
Calls dns v1 PUT /dns/v1/projects/{project}/responsePolicies/{responsePolicy}/rules/{responsePolicyRule}.
Updates an existing Response Policy Rule.
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
3 fields, 3 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 |
|---|---|---|---|---|---|
response_policy Response policy name or id. | string | Yes | — | — | — |
response_policy_rule Response policy rule name or id. | string | Yes | — | — | — |
body The ResponsePolicyRule resource, as the API defines it. | object | Yes | — | — | — |
Output
One shape.
result
Extra keys beyond the ones listed can appear.
| Field | Type | Example |
|---|---|---|
responsePolicyRule | object | — |
{
"responsePolicyRule": {}
}See Replace Response Policy Rule 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.