Establish Peering
netapp.establish_peering
ActionGoogle Cloudconnection required
Calls NetApp POST /v1/projects/{projectsId}/locations/{locationsId}/volumes/{volumesId}:establishPeering.
Establish volume peering. This is used to establish cluster and svm peerings between the GCNV and OnPrem clusters.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google NetApp
- Secret shape
- {"client_id", "client_secret", "refresh_token"}
- Config it needs
- location, project_id
- Resolved by
- config.connection_id, else node.connection_id
Configuration
4 fields, 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 |
|---|---|---|---|---|---|
project_id GCP project id (overrides connection). | string | No | — | — | — |
location Location / region (overrides connection). | string | No | — | — | — |
volume Id of the volume to act on, from netapp.list_volumes — not its name. | string | Yes | — | — | — |
body Request body (EstablishVolumePeeringRequest) as JSON. | object | No | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok | boolean | — |
response | object | — |
error | object | — |
done | boolean | — |
metadata | object | — |
name | string | — |
{
"done": false,
"error": {},
"metadata": {},
"name": "",
"ok": false,
"response": {}
}See Establish Peering run in a workflow.
In a technical demo we add the Google NetApp connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.