enumeray model revoke-publication

Permanently revoke one model publication while preserving accepted history.

Use when: A publication must stop authorizing new work, for example after an integrity or safety issue.

Role and prerequisites: Model 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 model revoke-publication scalar-double scalar-v1

For a broader revocation of every publication sharing one exact installation, contact Enumeray support. Revocation is permanent; changing the current pointer does not undo it.

Inputs and options

Input	Meaning and use
<ID>	Managed model ID.
<PUBLICATION>	Immutable publication ID from model publications or model release status. Inspect status before activation or revocation.

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

Result and next step

Revokes only the selected publication. Other publications using the same retained installation are not revoked by this API command. Accepted history is preserved; already accepted work is not cancelled.

Inspect model publications and current availability; activate a new ready candidate when a replacement is appropriate.

Exact syntax, defaults and accepted values

Permanently revoke this publication while preserving its accepted history

Usage: enumeray model revoke-publication [OPTIONS] <ID> <PUBLICATION>

Arguments:
  <ID>           Stable model ID from model list/get or supplied by its author
  <PUBLICATION>  Immutable publication ID from model publications or model release status

Options:
      --api <API>          User API origin override; credentials never cross origins. Host/runner commands use explicit configuration
      --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