enumeray model archive

Archive a model at an observed generation.

Use when: The owner is retiring it from active discovery and submission.

Role and prerequisites: Resource owner; co-admin status alone does not grant ownership changes. 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 model get scalar-double
enumeray model archive scalar-double --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
<ID>	Model ID you own.
--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

Marks the model archived while retaining accepted history. It does not delete installation files or cancel backend execution.

Inspect retained run history and arrange installation retirement with the connector owner.

Exact syntax, defaults and accepted values

Permanently archive the model at its observed model generation

Usage: enumeray model archive [OPTIONS] --generation <GENERATION> <ID>

Arguments:
  <ID>  Stable model ID from model list/get or supplied by its author

Options:
      --api <API>                User API origin override; credentials never cross origins. Host/runner commands use explicit configuration
      --generation <GENERATION>  Observed model generation from model get/members; shared by access and governance changes
      --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