Update Gateway

gcp_api_gateway.update_gateway
ActionGoogle Cloudconnection required

Calls apigateway v1 PATCH /v1/projects/{projectsId}/locations/{locationsId}/gateways/{gatewaysId}.

Updates the parameters of a single Gateway.

Connection

Required
Yes — the node will not save without one
Auth type
OAuth 2.0
Providers
Google API Gateway
Secret shape
{"client_id", "client_secret", "refresh_token"}
Config it needs
project_id, location
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.

FieldTypeRequiredDefaultConstraintsExample
location
Location or region; taken from the connection when unset.
stringNo———
gateway
Gateway name or id.
stringYes———
body
The ApigatewayGateway resource, as the API defines it.
objectYes———

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 Gateway run in a workflow.

In a technical demo we add the Google API Gateway connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.