enumeray setup status

Inspect saved setup progress and current authenticated readiness.

Use when: Check a partial journey, offline host or current readiness without initiating checks.

Role and prerequisites: The saved setup account with current connector inspection authority. 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 setup status --directory enumeray-setup

Inputs and options

Input	Meaning and use
--directory <DIRECTORY>	Existing private setup directory; inspection does not wait for its mutation writer.

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

Result and next step

Returns the saved plan and available diagnostics; missing observations remain unknown. No registration, check or repair is initiated.

Renew the original login or follow the responsible role’s correction, then resume setup.

Exact syntax, defaults and accepted values

Inspect saved progress and authenticated readiness without requesting checks

Usage: enumeray setup status [OPTIONS] --directory <DIRECTORY>

Options:
      --api <API>              User API origin override; credentials never cross origins. Host/runner commands use explicit configuration
      --directory <DIRECTORY>  Existing private setup checkpoint directory to inspect
      --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