Update Peering

managed_ad.update_peering

ActionGoogle Cloudconnection required

Calls managedidentities v1 PATCH /v1/projects/{projectsId}/locations/global/peerings/{peeringsId}.

Updates the labels for specified Peering.

Ask about Google Managed Service for Microsoft Active Directory All Google Managed Service for Microsoft Active Directory nodes Provider API docs ↗

Connection

Required: Yes — the node will not save without one
Auth type: OAuth 2.0
Providers: Google Managed Service for Microsoft Active Directory
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, 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
peering Peering name or id.	string	Yes	—	—	—
body The Peering resource, as the API defines it.	object	Yes	—	—	—
update_mask Mask of fields to update. Optional.	string	No	—	—	—

Output

One shape.

result

Extra keys beyond the ones listed can appear.

Field	Type	Example
done	boolean	—
error	object	—
metadata	object	—
name	string	—
response	object	—

{
  "done": false,
  "error": {},
  "metadata": {},
  "name": "",
  "response": {}
}

Related Google Managed Service for Microsoft Active Directory nodes

See Update Peering run in a workflow.

In a technical demo we add the Google Managed Service for Microsoft Active Directory connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.

Book a technical demo Talk to sales