osc object-store object delete

Permanently deletes an object from the object store. Object deletion occurs immediately at request time. Any subsequent GET, HEAD, POST, or DELETE operations will return a 404 Not Found error code. For static large object manifests, you can add the ?multipart- manifest=delete query parameter. This operation deletes the segment objects and, if all deletions succeed, this operation deletes the manifest object. A DELETE request made to a symlink path will delete the symlink rather than the target object. An alternative to using the DELETE operation is to use the POST operation with the bulk-delete query parameter

Usage: osc object-store object delete [OPTIONS] <CONTAINER> <OBJECT>

Arguments:

  • <CONTAINER> — The unique name for the account. An account is also known as the project or tenant
  • <OBJECT> — The unique name for the object

Options:

  • --multipart-manifest <MULTIPART_MANIFEST> — If you include the multipart-manifest=get query parameter and the object is a large object, the object contents are not returned. Instead, the manifest is returned in the X-Object-Manifest response header for dynamic large objects or in the response body for static large objects