enumeray run log-archive

Inspect terminal log archive metadata and retention availability.

Use when: Bounded live logs are insufficient and you need the 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 run log-archive 22222222-2222-4222-8222-222222222222

Inputs and options

Input	Meaning and use
<ID>	Accepted run UUID visible to your account.

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

Result and next step

Returns the archive status and any artifact metadata. Archives are diagnostic bytes, independently bounded/retained, and may be pending, unavailable or expired.

Download the returned artifact ID with artifact download; see logs and provenance.

Exact syntax, defaults and accepted values

Inspect the retained terminal diagnostic log archive reference

Usage: enumeray run log-archive [OPTIONS] <ID>

Arguments:
  <ID>  Accepted run UUID from run list/get or the saved acceptance receipt

Options:
      --api <API>          User API origin override; credentials never cross origins. Host/runner commands use explicit configuration
      --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