enumeray connector grant

Manage context-scoped compute grants.

Use when: Grant an author access to a selected connector context or discover your own available grants.

Role and prerequisites: Connector owner or current co-admin; transfer and membership changes are owner-only. 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 grant list lab-connector
enumeray connector grant available

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

Choose a subcommand

Command	Purpose
list	List compute grants managed by a connector.
create	Grant an account compute access to one execution context with bounded capacity.
get	Inspect a compute grant’s current limits, generation and revocation state.
update	Change a compute grant’s limits while retaining its identity and publications.
revoke	Revoke one connector compute grant.
available	Discover your active compute grants and their model-facing execution configuration.

Result and next step

Choose a subcommand below. A grant never grants connector administration or model access.

Inspect connector get and its context, grant and audit records before changing authority.

Exact syntax, defaults and accepted values

Grant explicit compute access to one context or discover your available grants

Usage: enumeray connector grant [OPTIONS] <COMMAND>

Commands:
  list       List this connector's context-scoped compute grants
  create     Give a user explicit compute access to one execution context
  get        Inspect current limits, generation and permanent revocation state
  update     Replace both capacity limits at the observed grant generation
  revoke     Permanently revoke one grant without substituting another grant
  available  Discover the compute grants available to your authenticated account
  help       Print this message or the help of the given subcommand(s)

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