HumDay

Lists assignments. Only explicitly created assignments will be in Google BigQuery Reservation

A documented Google BigQuery Reservation operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.

Automate this

What this operation does

Lists assignments. Only explicitly created assignments will be returned. Example: Organization organizationA contains two projects, project1 and project2. Reservation res1 exists…

  • GETReads data · projectsbigqueryreservation.googleapis.com/v1beta1/{parent}/assignments

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 BigQuery Reservation operations the program may use, and this is one of them.
  3. You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.

Other Google BigQuery Reservation operations

All 13 Google BigQuery Reservation operations

Questions

Can HumDay lists assignments. only explicitly created assignments will be in Google BigQuery Reservation?
Yes. This operation is published in Google BigQuery Reservation's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
Does this change anything in my Google BigQuery Reservation account?
No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Google BigQuery Reservation.
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 BigQuery Reservation account.

Where this came from

Read from a published API description for Google BigQuery Reservation at bigqueryreservation.googleapis.com/$discovery/rest?version=v1beta1. The description above is the provider’s own wording, not ours. Last published 2022-10-20.