Update Service Env
cloud_run.update_service_env
ActionGoogle Cloudconnection required
Calls Cloud Run Admin API v2 PATCH /services/{s}?updateMask=template.
Replace env vars on a Cloud Run service's first container (new revision).
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google Cloud Run
- Secret shape
- {"client_id", "client_secret", "refresh_token"}
- Config it needs
- project_id, region
- 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.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
project_id GCP project id (overrides connection). | string | No | — | — | — |
region Cloud Run region (overrides connection). | string | No | us-central1 | — | — |
service Service name. | string | Yes | — | — | — |
env Env vars as a JSON object {NAME: value}. | object | Yes | — | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"region": "us-central1"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok | boolean | — |
operation | string | — |
done | boolean | — |
{
"done": false,
"ok": false,
"operation": ""
}Notes
- Returns as soon as Cloud Run accepts the patch — the old revision is still serving. Add cloud_run.wait_operation before anything that talks to the service.
- Use cloud_run.update_service to change the image, resources or scaling in the same deploy.
Related Google Cloud Run nodes
See Update Service Env run in a workflow.
In a technical demo we add the Google Cloud Run connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.