enumeray run provenance

Inspect provenance metadata or download the immutable provenance content.

Use when: You need evidence of the inputs, publication, execution destination and retained output identities.

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 provenance 22222222-2222-4222-8222-222222222222
enumeray run provenance 22222222-2222-4222-8222-222222222222 --output provenance.json

Inputs and options

Input	Meaning and use
<ID>	Accepted run UUID visible to your account.
--output <OUTPUT>	Optional new local download path. It must not already exist; parent directory must exist. Omit to inspect metadata instead.

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

Result and next step

Without --output, prints metadata. With --output, downloads provenance content to a new local file; it does not rerun the science.

Retain provenance with downloaded scientific files for reproducibility.

Exact syntax, defaults and accepted values

Inspect or save immutable run provenance without downloading output bytes

Usage: enumeray run provenance [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
      --output <OUTPUT>    New private provenance JSON file; omit to print provenance without saving a file
      --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