enumeray connector grant get

Inspect a compute grant’s current limits, generation and revocation state.

Use when: You need the grant generation before changing capacity or resolving a lost update response.

Role and prerequisites: Connector owner, current co-admin or the grant holder; requires connectors:read. 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 get lab-connector 33333333-3333-4333-8333-333333333333

Inputs and options

Input	Meaning and use
<CONNECTOR>	Owning connector ID.
<GRANT_ID>	Compute-grant ID returned by connector grant create or listed by connector grant list; this is not a context ID.

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

Result and next step

Returns the stable grant ID, context, holder, both limits, generation and revocation timestamp.

Connector administrators use connector grant update with this observed grant generation and both explicit limits. Grant holders request capacity changes from their connector administrators.

Exact syntax, defaults and accepted values

Inspect current limits, generation and permanent revocation state

Usage: enumeray connector grant get [OPTIONS] <CONNECTOR> <GRANT_ID>

Arguments:
  <CONNECTOR>  Owning connector ID from connector list/get
  <GRANT_ID>   Compute-grant ID from connector grant list/create, not a context ID

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