HumDay

Deletes a sink. If the sink has a unique writeridentity in Google Cloud Logging

A documented Google Cloud Logging operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.

Automate this

What this operation does

Deletes a sink. If the sink has a unique writeridentity, then that service account is also deleted.

  • DELETEChanges data · sinkslogging.googleapis.com/v2/{sinkName}

How HumDay uses it

  1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
  2. The contract names it. Before anything is built, you see exactly which Google Cloud Logging operations the program may use, and this is one of them.
  3. You approve access. Because this one changes data, it cannot run until you have explicitly granted it.

Other Google Cloud Logging operations

All 39 Google Cloud Logging operations

Questions

Can HumDay deletes a sink. if the sink has a unique writeridentity in Google Cloud Logging?
Yes. This operation is published in Google Cloud Logging's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
Will this change my Google Cloud Logging data?
Yes — this is a DELETE operation, so it changes something in Google Cloud Logging. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
Do I need to write code?
No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Google Cloud Logging account.

Where this came from

Read from a published API description for Google Cloud Logging at logging.googleapis.com/$discovery/rest?version=v2. The description above is the provider’s own wording, not ours. Last published 2023-04-21.