pi-cliproxyapi-provider 0.16.0 → 0.16.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +5 -1
- package/data/models-dev-fallback.json +1 -1
- package/extensions/index.ts +0 -2
- package/package.json +1 -1
- package/src/catalog.ts +5 -2
- package/src/config.ts +57 -0
- package/src/registration.ts +1 -1
- package/src/runtime.ts +2 -2
- package/src/types.ts +1 -0
- package/src/auth.ts +0 -11
package/README.md
CHANGED
|
@@ -148,7 +148,11 @@ If you changed the provider name, use that name instead:
|
|
|
148
148
|
/login 0xdev
|
|
149
149
|
```
|
|
150
150
|
|
|
151
|
-
For non-interactive runs, set:
|
|
151
|
+
For non-interactive runs, optionally set `apiKey` in the global CPA config to a Pi credential expression. The command must be one of `bw get`, `op read`, `cat`, `secret-tool lookup`, `gpg --decrypt` (`-d`), `pass show`, or `security find-generic-password` (`find-internet-password`), for example `"apiKey": "!cat ~/.config/cpa-key"` or `"apiKey": "!op read op://Private/CLIProxyAPI/credential"`. Pi resolves the expression; saved or runtime credentials take precedence. Project config cannot set this field. When omitted, the legacy environment variable below is used. With `authRequired: false`, the configured expression is not used. Shell operators, other executables, and other subcommands are rejected when the config loads.
|
|
152
|
+
|
|
153
|
+
Keep secrets out of the command text. Pi includes the command verbatim in resolver errors, so a command that embeds a token can leak it into logs and notifications. Read the key from a file or a credential manager instead.
|
|
154
|
+
|
|
155
|
+
Alternatively, set:
|
|
152
156
|
|
|
153
157
|
```bash
|
|
154
158
|
export CLIPROXYAPI_API_KEY=your-key
|