enumeray connector context update

Change an execution context’s descriptive location and data disclosure.

Use when: Site description or data-handling disclosure changed while the execution definition stays the same.

Role and prerequisites: Connector owner or current co-admin. 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 context update lab-connector lab-process --location 'Lab Helsinki' --disclosure 'Lab operators can inspect execution data.' --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.

Inputs and options

Input	Meaning and use
<CONNECTOR>	Owning connector ID.
<CONTEXT>	Context ID from connector context list; use its generation, not the ownership or connector configuration generation.
--location <LOCATION>	Nonempty connector-owned description of where execution occurs. It is displayed to model users; it does not route work.
--disclosure <DISCLOSURE>	Nonempty connector-owned description of data access/handling. Authors cannot override it through a publication. This change affects future snapshots, not accepted run history.
--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.

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

Result and next step

Updates metadata at the observed context generation. These fields are connector-owned; already accepted work retains its snapshot.

Read connector context list again and review how future publications/runs disclose the destination.

Exact syntax, defaults and accepted values

Change descriptive location and data-access disclosure

Usage: enumeray connector context update [OPTIONS] --location <LOCATION> --disclosure <DISCLOSURE> --generation <GENERATION> <CONNECTOR> <CONTEXT>

Arguments:
  <CONNECTOR>  Owning connector ID from connector list/get
  <CONTEXT>    Execution-context ID registered under the selected connector

Options:
      --api <API>                User API origin override; credentials never cross origins. Host/runner commands use explicit configuration
      --location <LOCATION>      Nonempty description of the execution location shown to model users; does not route work
      --disclosure <DISCLOSURE>  Nonempty description of data access and handling; accepted runs retain their original snapshot
      --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
      --generation <GENERATION>  Observed context generation from connector context list/get; shared by metadata and lifecycle changes
      --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