enumeray artifact download

Download an artifact to a new path and verify its size and SHA-256 checksum.

Use when: You need local scientific output, reusable input data or a retained diagnostic archive.

Role and prerequisites: Authenticated model user with access to the resource. 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 download 33333333-3333-4333-8333-333333333333 --output result.csv

Inputs and options

Input	Meaning and use
<ID>	Verified artifact ID from artifact get, run artifacts or run log-archive.
--output <OUTPUT>	Local destination path; its parent must exist. Repeat the same command/path after interruption to resume verified bytes. The CLI prints its retained checkpoint location.

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

Result and next step

Retrieves the exact artifact version, resumes its private byte checkpoint and verifies the full size/SHA-256 before creating the requested file. Conflicting output paths are preserved.

Retain scientific bytes with run provenance; decode diagnostic archives only according to their documented format.

Exact syntax, defaults and accepted values

Download an exact artifact version with resumable size and SHA-256 verification

Usage: enumeray artifact download [OPTIONS] --output <OUTPUT> <ID>

Arguments:
  <ID>  Artifact UUID from upload completion, run artifacts or run log-archive; not a run ID

Options:
      --api <API>          User API origin override; credentials never cross origins. Host/runner commands use explicit configuration
      --output <OUTPUT>    Local destination file; parent must exist. Reuse this path to resume; conflicting files are preserved
      --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