stado storage
Invocation
stado storage <COMMAND>Purpose
Move queue state between storage backends (billing-outage migration)
Required inputs and options
This command has no command-specific inputs or options.
Output and state effect
This command group selects one of the subcommands listed below; use its exact child invocation to perform an operation.
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.
Subcommands
copy— Copy queue state from one storage backend to anotherbackup— Copy the active queue store to the configured disaster-recovery storels— List objects under a prefix, or per-prefix counts across the whole canonical prefix set when no prefix is givenstat— Report one object: present, absent, or unreachablecat— Write one object's body to stdoutverify— Compare two stores object-for-object. Read-only; copies nothingarchive— Package one directory as a deterministic gzip-compressed release archiveput— Upload a product object through the provider-neutral Stado namespace. Release objects are always create-only, even without --if-absentget— Download a product object through the provider-neutral Stado namespaceobjects— List product objects in one provider-neutral Stado namespaceabort-upload— Discard the staged parts of one interrupted multipart uploadrm— Delete a product object through the provider-neutral Stado namespace. Release objects are immutable and cannot be deletedurl— Print the gateway URL; only stado://releases/... is bearer-free