Deletes a WorkerPool in Google Cloud Build

What this operation does

Deletes a WorkerPool.

• DELETEChanges data · projectscloudbuild.googleapis.com/v1alpha2/{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 Build 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 Build operations

• Creates a WorkerPool to run the buildsPOST · changes data
• Updates a WorkerPoolPATCH · changes data
• Starts asynchronous cancellation on a long-running operationPOST · changes data
• Returns details of a WorkerPoolGET · reads data
• Lists WorkerPools by projectGET · reads data

All 6 Google Cloud Build operations

Questions

Can HumDay deletes a workerpool in Google Cloud Build?

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

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

Where this came from

Read from a published API description for Google Cloud Build at cloudbuild.googleapis.com/$discovery/rest?version=v1alpha2. The description above is the provider’s own wording, not ours. Last published 2022-12-05.