enumeray connector context replacement-plan
Inspect paginated replacement dependencies and actions with responsible roles.
Use when: You are coordinating author handoffs or decommissioning a context before closing new use.
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
Section titled “Example”enumeray connector context replacement-plan lab-connector lab-cpu --replacement lab-cpu-nextenumeray connector context replacement-plan lab-connector lab-cpu --replacement lab-cpu-next --section runs --limit 20Connector authority permits operational metadata; scientific inputs, outputs, logs and referenced artifacts still require separate authorization. See the replacement workflow.
Inputs and options
Section titled “Inputs and options”| Input | Meaning and use |
|---|---|
<CONNECTOR> |
Owning connector ID from connector list/get. |
<CONTEXT> |
Source context ID from connector context list. Its generation is separate from ownership and connector configuration generations. |
--replacement <REPLACEMENT> |
Fresh active replacement context ID. Another connector is permitted only when you currently administer both connectors; accepted work keeps its original context and connector. |
--section <SECTION> |
Dependency page to inspect: publications (default), grants or runs. Each section has its own pagination. |
--limit <LIMIT> |
Maximum dependencies in this page, from 1 through 100. Repeat with the returned cursor for additional records. |
--cursor <CURSOR> |
Opaque continuation cursor returned for this dependency section. Preserve it unchanged and keep the same source, replacement and section. |
Every command also accepts the profile, API, JSON and timeout options.
Result and next step
Section titled “Result and next step”Returns operational source/replacement state, dependent publications including candidates, grants, affected work and delivery obligations, plus required actions. It does not write lifecycle or audit records.
Provision a fresh context and grants, then ask authors to register, validate, trial, review and explicitly activate fresh publications.
Exact syntax, defaults and accepted values
Inspect replacement dependencies and actions for connector owners and authors
Usage: enumeray connector context replacement-plan [OPTIONS] <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
--replacement <REPLACEMENT> Optional replacement context ID; requires administration of its connector and does not migrate publications or grants
--profile <PROFILE> Named local user API/login profile; host/runner commands use explicit configuration
[default: default]
--section <SECTION> Dependency collection to inspect on this page
Possible values: - publications: Dependent publications and author handoff actions - grants: Context-scoped compute grants and their replacement actions - runs: Accepted runs and outstanding execution or delivery obligations
[default: publications]
--config <CONFIG> Private user profiles file; defaults to $XDG_CONFIG_HOME/enumeray/profiles.json or ~/.config/enumeray/profiles.json
--limit <LIMIT> Maximum entries on this page (1–100); omit for the API default
--cursor <CURSOR> Continuation from the preceding page; pass unchanged with the same filters
--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 (see a summary with '-h')Documentation 205dcb3116ea · public sources 8c70356d340f · built .Download documentation identity.