Update Volume

netapp.update_volume
ActionGoogle Cloudconnection required

Calls netapp v1 PATCH /v1/projects/{projectsId}/locations/{locationsId}/volumes/{volumesId}.

Updates the parameters of a single Volume.

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
project_id, location
Resolved by
config.connection_id, else node.connection_id

Configuration

4 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
location
Location or region; taken from the connection when unset.
stringNo———
volume
Volume name or id.
stringYes———
body
The Volume resource, as the API defines it.
objectYes———
update_mask
Field mask is used to specify the fields to be overwritten in the Volume resource by the update. Optional.
stringNo———

Output

One shape.

result

Extra keys beyond the ones listed can appear.

FieldTypeExample
done
boolean—
error
object—
metadata
object—
name
string—
response
object—
{
  "done": false,
  "error": {},
  "metadata": {},
  "name": "",
  "response": {}
}

See Update Volume 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.