Set or clear a volume's storage cap
Authorizations
Organization API key (msb_…) - org-scoped programmatic access.
Path Parameters
Volume id
Body
PATCH /v1/orgs/{slug}/volumes/{id} - update the cap and/or labels (#496).
Every field is independently optional: an omitted field is left unchanged.
capacity_gib uses the double-Option distinction - omit to leave as-is,
explicit null to clear the cap, a number to set it.
New per-volume storage cap in GiB. Omitted = unchanged; null = clear the
cap (back to no per-volume limit); a value sets it. A set value must be
>= 1 and <= the org's storage cap.
x >= 0Replacement label set. Omitted = unchanged; an object replaces the labels wholesale (an empty object clears them). Reserved-prefix keys are rejected.
Response
Volume updated
Volume metadata returned in list/create responses. The GCS storage path is derived (not stored) and never exposed.
host - the org's shared host disk (not deletable); managed - a
user-created named volume.
host, managed User-defined labels (empty object when none set).
Lifecycle status of a volume.
active, deleting How the volume is physically backed (block today).
block The volume's configured per-volume storage cap in bytes, or null when
no cap is set (#496). Derived from the stored capacity_gib (the user's
configured intent) - the effective ceiling is min(this, org cap).
x >= 0User-facing name. null for the host volume (it has no name; it's
identified by kind).
Bytes currently used under this volume's subtree. null when usage is
unavailable - the usage service is disabled or unreachable (list degrades
gracefully rather than failing) - or on create/delete, which don't sample
it.
x >= 0