Delete a volume version
Deletes the version the address names, along with every tag pointing at it. Addressing the version by tag deletes the version the tag points at, not the tag. The data is not erased: the version stays restorable until the recovery deadline in the response passes. Deleting a version that is already deleted is a conflict, not a repeat success.
Authorizations
Send Authorization: Bearer <api_key>. The legacy Authorization: Api-Key <api_key> scheme is also accepted.
Path Parameters
Body
Revision the volume is expected to be at. When set, the delete fails with a conflict if the volume has changed since, so a read followed by a delete cannot act on a version a tag has since been moved off. Take the value from volume_sequence.
Response
Namespace the volume belongs to, in lowercase.
Name of the volume, in lowercase.
Full address of the deleted version, as bdn:<namespace>/<volume>@<digest>.
Content digest of the deleted version, as b3:<hex>.
Lifecycle state of the version after the delete.
When the version stops being restorable, in ISO 8601 format. Until then it can be returned to service.
Revision of the volume after the delete.