Delete Sink

cloud_logging.delete_sink
ActionGoogle Cloudconnection required

Calls DELETE /projects/{project}/sinks/{sink}.

Delete a log export sink from a project.

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

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

FieldTypeRequiredDefaultConstraintsExample
project_id
GCP project id (overrides connection).
stringNo———
sink_name
Sink id to delete.
stringYes———
ignore_missing
Succeed when the sink is already gone, so a re-run converges.
booleanNotrue——

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "ignore_missing": true
}

Output

One shape.

result

FieldTypeExample
ok
boolean—
name
Sink id that was targeted.
string—
deleted
True when this run removed the sink.
boolean—
missing
True when the sink was already gone and ignore_missing was set.
boolean—
{
  "deleted": false,
  "missing": false,
  "name": "",
  "ok": false
}

Solutions with Google Cloud Logging

See Delete Sink 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.