Update commitment. If commitment auto-assignment is enabled, it will additionally create missing matching assignments.

Path Params
string
required
Body Params

Commitments

string
enum
Defaults to Inactive
  • Inactive: Inactive commitment
  • Active: Active commitment
Allowed:
float | null

Allowed usage specifies the part of the commitment that is allowed to be used. 1.0 means 100% of the commitment. Currently it's only supported for GCP CUDs.

boolean | null
string
enum
Defaults to Default

Scaling strategy specifies how to use commitment by autoscaler.

  • Default: If some commitment resource is utilised fully, only part of instance type can be covered by this commitment. In some cases not using commitment will be cheaper and cheaper option will be chosen by autoscaler.
  • CPUBased: Aim to use as much CPU from commitment as possible. Even if instance is partially covered and cheaper option is available.
  • RamBased: Aim to use as much RAM from commitment as possible. Even if instance is partially covered and cheaper option is available.
Allowed:
boolean | null

Assign commitment to all existing and future clusters that fall within the region of this commitment.

Response

Language
Credentials
URL
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json