Update Database
spanner.update_database
ActionGoogle Cloudconnection required
Calls spanner v1 PATCH /v1/projects/{projectsId}/instances/{instancesId}/databases/{databasesId}.
Updates a Cloud Spanner database.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google Cloud Spanner
- Secret shape
- {"client_id", "client_secret", "refresh_token"}
- Config it needs
- project_id, instance, database
- Resolved by
- config.connection_id, else node.connection_id
Configuration
4 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 |
|---|---|---|---|---|---|
instance Instance name or id. | string | Yes | — | — | — |
database Database name or id. | string | Yes | — | — | — |
body The Database resource, as the API defines it. | object | Yes | — | — | — |
update_mask The list of fields to update. Optional. | string | No | — | — | — |
Output
One shape.
result
Extra keys beyond the ones listed can appear.
| Field | Type | Example |
|---|---|---|
done | boolean | — |
error | object | — |
metadata | object | — |
name | string | — |
response | object | — |
{
"done": false,
"error": {},
"metadata": {},
"name": "",
"response": {}
}Related Google Cloud Spanner nodes
See Update Database run in a workflow.
In a technical demo we add the Google Cloud Spanner connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.