enumeray artifact resume

Resume an upload’s reservation, byte transfer or verified completion.

Use when: A saved upload did not return a definite completion after timeout, restart or network interruption.

Role and prerequisites: Original upload account with uploads:create, uploads:read and uploads:complete; an unreserved saved operation can still need reservation creation. Install enumeray, configure the API and log in. Use an account or delegated token with the required permissions. Example IDs must be replaced with IDs from your service.

Example

enumeray artifact resume --state upload-state.json

Inputs and options

Input	Meaning and use
--state <STATE>	Original private upload-operation file created by artifact upload. Reuse it with the same API/account and unchanged source bytes: it retains the checksum, reservation and retry identity. A new state file requests another upload rather than recovering this one.

Every command also accepts the profile, API, JSON and timeout options.

Result and next step

Reuses the same source digest, request identity and upload reservation. It validates state and source instead of silently accepting changed bytes.

Reuse the resulting verified reference in analysis inputs; preserve the state if recovery remains uncertain.

Exact syntax, defaults and accepted values

Resume reservation, transfer, or completion using the saved operation

Usage: enumeray artifact resume [OPTIONS] --state <STATE>

Options:
      --api <API>          User API origin override; credentials never cross origins. Host/runner commands use explicit configuration
      --state <STATE>      Original private upload-state JSON file; reuses the source digest and request identity
      --profile <PROFILE>  Named local user API/login profile; host/runner commands use explicit configuration [default: default]
      --config <CONFIG>    Private user profiles file; defaults to $XDG_CONFIG_HOME/enumeray/profiles.json or ~/.config/enumeray/profiles.json
      --json               Emit user API results as JSON (NDJSON for following logs) and runtime errors on stderr; host/runner output follows its own protocol
      --timeout <TIMEOUT>  User API HTTP timeout in seconds; live logs use it for read inactivity. Does not limit execution time [default: 60]
  -h, --help               Print help