ewilliams28/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-08-12 21:53:00 -06:00
Code Issues Packages Projects Releases Wiki Activity

feat(secrets): add SQLite-backed secret store (#121559)

Browse Source
This commit is contained in:
Peter Steinberger
2026-08-10 07:08:40 -07:00
committed by GitHub
parent b121219a44
commit f4bac99a81
81 changed files with 4455 additions and 2611 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/start/wizard-cli-reference.md
+1 -1
View File
@@ -303,7 +303,7 @@ Credential storage mode:
- In non-interactive mode, `--secret-input-mode ref` creates only env-backed references for new credentials.
- Set the provider env var in the onboarding process environment when adding a new credential.
- Inline key flags (for example `--openai-api-key`) require that env var to be set; otherwise onboarding fails fast.
- Existing resolvable named auth profiles are reused unchanged, including existing `env`, `file`, and `exec` references; no new `apiKey` or `keyRef` is written and no additional provider env var is required.
- Existing resolvable named auth profiles are reused unchanged, including existing `env`, `file`, `exec`, and `store` references; no new `apiKey` or `keyRef` is written and no additional provider env var is required.
- For new custom-provider credentials, non-interactive `ref` mode stores `models.providers.<id>.apiKey` as `{ source: "env", provider: "default", id: "CUSTOM_API_KEY" }`.
- In that custom-provider case, `--custom-api-key` requires `CUSTOM_API_KEY` to be set; otherwise onboarding fails fast.
- Existing plaintext profile credentials remain unchanged; reference mode does not migrate them. Run `openclaw secrets configure --apply`, then `openclaw secrets audit --check`. See [Secrets management](/gateway/secrets).