Update Capacity Commitment

bigquery_reservation.update_capacity_commitment

ActionGoogle Cloudconnection required

Calls bigqueryreservation v1 PATCH /v1/projects/{projectsId}/locations/{locationsId}/capacityCommitments/{capacityCommitmentsId}.

Updates an existing capacity commitment.

Ask about Google BigQuery Reservation All Google BigQuery Reservation nodes Provider API docs ↗

Connection

Required: Yes — the node will not save without one
Auth type: OAuth 2.0
Providers: Google BigQuery Reservation
Secret shape: {"client_id", "client_secret", "refresh_token"}
Config it needs: project_id, location
Resolved by: config.connection_id, else node.connection_id

Configuration

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

Field	Type	Required	Default	Constraints	Example
location Location or region; taken from the connection when unset.	string	No	—	—	—
capacity_commitment Capacity commitment name or id.	string	Yes	—	—	—
body The CapacityCommitment resource, as the API defines it.	object	Yes	—	—	—

Output

One shape.

result

Extra keys beyond the ones listed can appear.

Field	Type	Example
commitmentEndTime	string	—
commitmentStartTime	string	—
edition	string	—
failureStatus	object	—
isFlatRate	boolean	—
multiRegionAuxiliary	boolean	—
name	string	—
plan	string	—
renewalPlan	string	—
slotCount	string	—
state	string	—

{
  "commitmentEndTime": "",
  "commitmentStartTime": "",
  "edition": "",
  "failureStatus": {},
  "isFlatRate": false,
  "multiRegionAuxiliary": false,
  "name": "",
  "plan": "",
  "renewalPlan": "",
  "slotCount": "",
  "state": ""
}

Related Google BigQuery Reservation nodes

See Update Capacity Commitment run in a workflow.

In a technical demo we add the Google BigQuery Reservation connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.

Book a technical demo Talk to sales