enumeray connector update

Apply a guarded maintenance state from a JSON management request.

Use when: An existing script uses the legacy maintenance request file; new workflows should use maintenance/resume.

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

cat > connector-state.json <<'JSON'
{"expected_generation":1,"draining":true}
JSON
enumeray connector update lab-connector --file connector-state.json

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.

Inputs and options

Input	Meaning and use
<ID>	Existing connector ID.
--file <FILE>	JSON request containing only expected_generation and boolean draining. true pauses new acceptance/claims and retains queued work; false permits eligible work again. Independent authority remains in force.

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

Result and next step

Inspects diagnostics and displays the same effects/counts as maintenance/resume, then sends the supplied guarded state request. This changes only maintenance and never execution authority.

Use wait-maintenance with the returned generation; see maintenance and authority controls.

Exact syntax, defaults and accepted values

Apply a guarded maintenance state from a JSON request; prefer maintenance/resume

Usage: enumeray connector update [OPTIONS] --file <FILE> <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
      --file <FILE>        JSON object with expected_generation and boolean draining; prefer maintenance/resume
      --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