Update Service
service_directory.update_service
ActionGoogle Cloudconnection required
Calls servicedirectory v1 PATCH /v1/projects/{projectsId}/locations/{locationsId}/namespaces/{namespacesId}/services/{servicesId}.
Updates a service.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google Service Directory
- Secret shape
- {"client_id", "client_secret", "refresh_token"}
- Config it needs
- project_id, location
- Resolved by
- config.connection_id, else node.connection_id
Configuration
5 fields, 3 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 |
|---|---|---|---|---|---|
location Location or region; taken from the connection when unset. | string | No | — | — | — |
namespace Namespace name or id. | string | Yes | — | — | — |
service Service name or id. | string | Yes | — | — | — |
body The Service resource, as the API defines it. | object | Yes | — | — | — |
update_mask List of fields to be updated in this request. Optional. | string | No | — | — | — |
Output
One shape.
result
Extra keys beyond the ones listed can appear.
| Field | Type | Example |
|---|---|---|
annotations | object | — |
endpoints | array | — |
name | string | — |
uid | string | — |
{
"annotations": {},
"endpoints": [],
"name": "",
"uid": ""
}Related Google Service Directory nodes
See Update Service run in a workflow.
In a technical demo we add the Google Service Directory connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.