Update commitment. If commitment auto-assignment is enabled, it will additionally create missing matching assignments.Ask AIput https://api.cast.ai/v1/savings/commitments/{commitmentId}Path ParamscommitmentIdstringrequiredBody ParamsCommitmentsstatusstringenumDefaults to Inactive Inactive: Inactive commitment Active: Active commitment InactiveActiveAllowed:InactiveActiveallowedUsagefloat | nullAllowed 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.prioritizationboolean | nulltruefalsescalingStrategystringenumDefaults to DefaultScaling 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. DefaultCPUBasedRamBasedAllowed:DefaultCPUBasedRamBasedautoAssignmentboolean | nullAssign commitment to all existing and future clusters that fall within the region of this commitment.truefalseResponse 200A successful response.Updated 7 months ago