Updates a sink. This method updates fields in the existing sink in Google Cloud Trace

What this operation does

Updates a sink. This method updates fields in the existing sink according to the provided update mask. The sink's name cannot be changed nor any output-only fields (e.g. the write…

• PATCHChanges data · projectscloudtrace.googleapis.com/v2beta1/{name}

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 Trace 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 Trace operations

• Creates a sink that exports trace spans to a destinationPOST · changes data
• Deletes a sinkDELETE · changes data
• List all sinks for the parent resource (GCP project)GET · reads data
• Get a trace sink by name under the parent resource (GCP project)GET · reads data

All 5 Google Cloud Trace operations

Questions

Can HumDay updates a sink. this method updates fields in the existing sink in Google Cloud Trace?

Yes. This operation is published in Google Cloud Trace'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 Trace data?

Yes — this is a PATCH operation, so it changes something in Google Cloud Trace. 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 Trace account.

Where this came from

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