Update Sink Projects

cloud_logging.update_sink_projects
ActionGoogle Cloudconnection required

Calls logging v2 PATCH /v2/projects/{projectsId}/sinks/{sinksId}.

Updates a sink.

Connection

Required
Yes — the node will not save without one
Auth type
OAuth 2.0
Providers
Google Cloud Logging
Secret shape
{"client_id", "client_secret", "refresh_token"}
Config it needs
project_id
Resolved by
config.connection_id, else node.connection_id

Configuration

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

FieldTypeRequiredDefaultConstraintsExample
sink
Sink name or id.
stringYes———
body
The LogSink resource, as the API defines it.
objectYes———

Output

One shape.

result

Extra keys beyond the ones listed can appear.

FieldTypeExample
bigqueryOptions
object—
createTime
string—
description
string—
destination
string—
disabled
boolean—
exclusions
array—
filter
string—
includeChildren
boolean—
interceptChildren
boolean—
name
string—
outputVersionFormat
string—
resourceName
string—
updateTime
string—
writerIdentity
string—
{
  "bigqueryOptions": {},
  "createTime": "",
  "description": "",
  "destination": "",
  "disabled": false,
  "exclusions": [],
  "filter": "",
  "includeChildren": false,
  "interceptChildren": false,
  "name": "",
  "outputVersionFormat": "",
  "resourceName": "",
  "updateTime": "",
  "writerIdentity": ""
}

Solutions with Google Cloud Logging

See Update Sink Projects run in a workflow.

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