stado storage abort-upload
Invocation
stado storage abort-upload [OPTIONS] <URI>Purpose
Discard the staged parts of one interrupted multipart upload. `put` stages a large body as `<key>.__stado_upload/<upload-id>/<index>` parts and composition promotes them in one step, deleting the parts as it goes. A publisher that dies between the last part and composition leaves the parts and no object: on 2026-09-04 the `stado` 0.15.25 darwin-arm64 archive sat as 19 unfinalised parts, 57 MiB of a coordinate nothing could read, and nothing in the product could remove them - `rm` refuses the whole `releases` namespace as immutable, which is true of published objects and false of staged parts. The object API already authorizes a part's DELETE against its TARGET's publisher, so the boundary for this was in place and only the command was missing.
Required inputs and options
| Input or option | Contract |
|---|---|
<URI> | The TARGET object whose staged parts are discarded, as `stado://<namespace>/<key>` - not a part's own URI. The parts are addressed relative to the object they were going to become, which is the only name a publisher knows after it has failed |
--dry-run | Report the parts and delete nothing |
--json | Command option; required or optional as shown in the invocation. |
Output and state effect
It performs the operation described above and emits its operator result on standard output or standard error. Any state change is limited to the resources and records named by the purpose and options on this page.
Refusals
- Before dispatch, Stado refuses a missing required token shown in the invocation, an unknown option, or a value outside a listed value set; argument-usage failures exit with code 2.