Quota API

Returns effective quota limits, inherited policy, and held reservations.

Requires projects:read. Each entry identifies dimension, optional region, explicit limit, inherited policy, effective limit, reserved usage, and remaining admission.

Memory uses MiB, persistent and ephemeral disk allocations use GiB, and count dimensions use resource counts. Retained-data dimensions identify their unit explicitly. Clients must not combine a byte measurement with a GiB quota value.

Updates explicit quota overrides.

Requires the quota-set ETag and quota-administration permission. Send an entries array of changed dimensions. Each entry has dimension, optional region_id, and a non-negative integer limit.

To limit the project to the specified vCPU and memory reservations, send:

{
  "entries": [
    { "dimension": "vcpus", "limit": 96 },
    { "dimension": "memory_mib", "region_id": "reg_euwest", "limit": 196608 }
  ]
}

Unmentioned dimensions remain unchanged. Duplicate dimension/region pairs, negative values, fractions, and unknown dimension names return 422 without applying the submitted set. Zero blocks new reservation increases.

An override cannot exceed a binding organization ceiling. An existing reservation above a reduced limit becomes over quota but is not terminated. The response returns the updated effective limits with 200.

Removes an explicit override and restores its inherited limit.

Requires the quota-set ETag. It removes that explicit override and returns the new inherited result. It does not remove the dimension's organization policy.

Inspect the effective value before admitting another deployment; inheritance can be more restrictive than the removed override.

Returns reservations and their owning resource or operation IDs.

Supports dimension, region, resource ID, and operation ID filters. It returns the holding ID, amount, lifecycle, and pending cleanup reference.

There is no blind release endpoint for a reservation whose resource state is uncertain. Resolve the original operation or deletion cleanup. Releasing a row without removing its actual resource could permit usage beyond the policy.

Use quotas, ephemeral disks, and operation recovery to interpret retained allocations.