feat: default macOS credentials to file backend#937
Conversation
|
Tom seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
44f38d7 to
6cfa46d
Compare
Summary
Default macOS credential storage to the local encrypted file backend so local automation, headless sessions, and AI agent workflows are not interrupted by Keychain prompts. Keep explicit backend selection via
LARKSUITE_CLI_KEYCHAIN_BACKENDforfile,auto, andkeychain.Changes
LARKSUITE_CLI_KEYCHAIN_BACKEND=file|auto|keychainbackend selection.filethe default macOS backend for AppSecret and UAT storage.autofor the previous Keychain-first behavior with file fallback.Test Plan
go test ./internal/keychain ./internal/credential ./internal/authlark-cli --versioncommand works as expected aftermake install PREFIX=/opt/homebrewRelated Issues
Notes
This PR intentionally changes the macOS default from Keychain/auto behavior to file-backed storage. Existing Keychain-backed installs may need migration handling or an explicit compatibility decision before the PR is marked ready.