enumeray connector resume

Preview or leave maintenance without restoring withdrawn execution authority.

Use when: The original connector service is running again and may accept eligible work.

Role and prerequisites: Connector owner or current co-admin. Inspection and dry-run require connectors:read; applying additionally requires connectors:manage. 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 connector diagnostics lab-connector
enumeray connector resume lab-connector --generation 1 --dry-run
enumeray connector resume lab-connector --generation 1

Resource names and UUIDs below are examples. Replace them with IDs returned by your service; --generation 1 is valid only if the latest response reports generation 1. The CLI inspects before applying and never refreshes a stale generation or retries an uncertain mutation. Re-read diagnostics and audit after a conflict or lost reply. Counts describe the inspection snapshot and can change as work progresses.

Inputs and options

Input	Meaning and use
<ID>	Existing connector ID from connector get/list.
--generation <GENERATION>	Observed resource generation from the relevant get, members, policy or limits response. This is an optimistic concurrency check, not a release number. Read again after a conflict; do not blindly increment it.
--dry-run	Read diagnostics and show the observed/proposed controls, affected work counts and effects without changing the connector or writing an audit event.

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

Result and next step

Clears only draining at the supplied generation. Connector authority, credentials, publication and installation revocations, grants, user access and readiness remain independent.

Inspect diagnostics and acceptance availability; use restore-authority separately if that reversible control was withdrawn.

Exact syntax, defaults and accepted values

Permit acceptance and claims without restoring withdrawn authority

Usage: enumeray connector resume [OPTIONS] --generation <GENERATION> <ID>

Arguments:
  <ID>  Stable connector ID from connector list/get

Options:
      --api <API>                User API origin override; credentials never cross origins. Host/runner commands use explicit configuration
      --generation <GENERATION>  Observed connector configuration generation from connector diagnostics/get
      --dry-run                  Inspect the observed and proposed change without applying it
      --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