enumeray connector inspect

Inspect journal identity and retained assignment IDs without inputs or secrets.

Use when: You need local diagnostic evidence before recovery or to correlate a host journal with API assignments.

Role and prerequisites: Connector host operator with access to the private journal. The binary and existing journal are sufficient; API credentials are not required.

Example

enumeray connector inspect --journal ./connector-state/journal

Inputs and options

Input	Meaning and use
--journal <JOURNAL>	Private durable journal directory. Reuse the same path after restart and never copy it to create another active connector. It contains ownership and backend execution evidence.

Host commands use explicit connector credentials or the private journal and emit JSON results; compute-runner uses only its stdin protocol and directory. User profile and API override options do not apply.

Result and next step

Prints a read-only snapshot without taking the journal process lock or creating lock files, including while the service is running. It does not contact the API, claim assignments or launch work.

A connector administrator can correlate these IDs with enumeray connector diagnostics CONNECTOR. A host operator without administration should provide the connector and assignment IDs to service support. Follow stopped-owner recovery procedures before mutation.

Exact syntax, defaults and accepted values

Show journal identities and prepared assignment IDs, without inputs or secrets

Usage: enumeray connector inspect [OPTIONS] --journal <JOURNAL>

Options:
      --api <API>          User API origin override; credentials never cross origins. Host/runner commands use explicit configuration
      --journal <JOURNAL>  Existing private durable journal to inspect without taking its process lock
      --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