enumeray analysis import

Import a retained prepared operation into a private analysis directory without contacting the API.

Use when: You retained a legacy file from the former run prepare command, including after a submission whose reply was lost.

Role and prerequisites: Holder of a private prepared-operation file; subsequent remote commands require the original API/account. Offline import requires only the installed CLI and retained private prepared-operation file. No configured profile, login, credentials or running API is required. Authenticate to the original API/account before subsequent status or submission commands.

Example

enumeray analysis import --prepared prepared-run.json --directory imported-analysis
enumeray analysis status imported-analysis
enumeray analysis submit imported-analysis

No saved receipt does not mean no run. Only explicit analysis submit can send the original request; status, logs and import never submit automatically. Completed artifact/collection references need no re-upload. The file contains no original local source bytes or earlier upload checkpoints. If both operation identity and receipt are lost, inspect authorized run history; never silently submit a replacement.

Inputs and options

Input	Meaning and use
--prepared <PREPARED>	Existing private PreparedRun JSON file written by the former run prepare command. Keep the original unchanged; import does not re-prepare or invent a replacement key.
--directory <DIRECTORY>	New private analysis directory, or the same interrupted import destination. Existing unrelated paths and conflicting evidence are preserved.

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

Result and next step

Validates the local format and retains the original API/account, request, publication, purpose/delegation and idempotency key. Preserves the source file and uncertain acceptance state. Import needs no configured profile or credentials and sends no request.

Authenticate to the original API/account, review the saved request, then explicitly run analysis submit to reconcile or obtain acceptance with the same request.

Exact syntax, defaults and accepted values

Import an original prepared request locally. Submit explicitly to reconcile acceptance

Usage: enumeray analysis import [OPTIONS] --prepared <PREPARED> --directory <DIRECTORY>

Options:
      --api <API>              User API origin override; credentials never cross origins. Host/runner commands use explicit configuration
      --prepared <PREPARED>    Original private prepared-operation JSON file from the former run prepare workflow
      --directory <DIRECTORY>  New private analysis directory, or the same interrupted import destination
      --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