enumeray connector grant create

Grant an account compute access to one execution context with bounded capacity.

Use when: A model author is approved to use a context for installation validation and publication.

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

enumeray connector grant create lab-connector --context lab-process --user 11111111-1111-4111-8111-111111111111 --max-queued-runs 100 --max-outstanding-assignments 4

Inputs and options

Input	Meaning and use
<ID>	Connector ID owning the chosen context.
--context <CONTEXT>	Execution-context ID from connector context list or connector grant available. Choose the context containing the approved driver/connection and intended disclosure.
--user <USER>	Stable UUID of the target account, obtained from auth whoami for yourself or from the service administrator for another account. Display labels and email addresses are not user IDs.
--max-queued-runs <MAX_QUEUED_RUNS>	Maximum accepted queued runs covered by this policy or grant. Use a positive integer; lowering a limit does not remove work already accepted.
--max-outstanding-assignments <MAX_OUTSTANDING_ASSIGNMENTS>	Dispatch capacity for assignments already given to the connector or using the compute grant. Slurm queue entries and unfinished assignments occupy capacity too; this is not a count of completed runs.

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

Result and next step

Creates a compute-grant record. It does not grant access to a model or make any publication current.

The grantee verifies it with connector grant available, then completes publication.json.

Exact syntax, defaults and accepted values

Give a user explicit compute access to one execution context

Usage: enumeray connector grant create [OPTIONS] --context <CONTEXT> --user <USER> <ID>

Arguments:
  <ID>  Stable connector ID from connector list/get

Options:
      --api <API>
          User API origin override; credentials never cross origins. Host/runner commands use explicit configuration
      --context <CONTEXT>
          Execution-context ID registered under the selected connector
      --profile <PROFILE>
          Named local user API/login profile; host/runner commands use explicit configuration [default: default]
      --user <USER>
          Stable UUID of the account receiving compute access to this context
      --config <CONFIG>
          Private user profiles file; defaults to $XDG_CONFIG_HOME/enumeray/profiles.json or ~/.config/enumeray/profiles.json
      --max-queued-runs <MAX_QUEUED_RUNS>
          Maximum accepted queued runs covered by this limit; lowering it preserves accepted work [default: 100]
      --json
          Emit user API results as JSON (NDJSON for following logs) and runtime errors on stderr; host/runner output follows its own protocol
      --max-outstanding-assignments <MAX_OUTSTANDING_ASSIGNMENTS>
          Dispatch capacity for unfinished assignments, including queued Slurm allocations [default: 4]
      --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