orke settings secret set
Store a key from stdin; Decision-1 requires endpoint/deployment/apiKey JSON.
When to use it
Store a key from stdin; Decision-1 requires endpoint/deployment/apiKey JSON.
Syntax
Terminal
orke settings secret set --key <nvidia|jev|microsoft-decision> --stdin [--json]Options
| Option | Required | Values and meaning |
|---|---|---|
--key | Required | Stored connection kind; reads never return its secret.nvidia|jev|microsoft-decision |
--stdin | Required | Read strict UTF-8 input through standard input. |
Read common options and errors →
Role and constraints
operator · Windows, macOS, Linux
- Never pass a secret as a command-line value. This saves credentials without making a model request.
- Requires a running daemon owned by the same OS user; --help never connects.
- Secret input requires --stdin; never put secrets in command-line values.
- The Get-Content pipe example uses PowerShell; file < redirection uses POSIX shell syntax. File contents travel through stdin, never argv.
- NVIDIA/Jev accept raw keys with trailing CR/LF removed. microsoft-decision accepts {"endpoint":"https://…","deployment":"…","apiKey":"…"}. Maximum lengths: endpoint 512, deployment 64, apiKey 4096; reads never return secrets.
Examples
Terminal
Get-Content -Raw ./secret.txt | orke settings secret set --key nvidia --stdin --jsonTerminal
orke settings secret set --key nvidia --stdin --json < ./secret.txtReplace example IDs, slugs, revisions, and files with actual observations and inputs.
Response and partial results
Inspect replies and errors with --json. Acceptance is not work completion.