bk config credential_store setting controls auth credential storage

Introduced 2026-06-09 · score 0.96

HOW TO USE IT

When configuring where `bk auth login` stores credentials, set the user-level `credential_store` key to `auto`, `keyring`, or `shm`; the CLI documents `shm` for in-memory `/dev/shm` storage.

WHY THIS HELPS

Configure bk's credential store for authentication commands.

BEFORE THIS CHANGE

Use `bk auth login --credential-store <auto|keyring|shm>` to select the store on that login invocation.

REQUIREMENTS AND LIMITATIONS

• Version: v3.47.0
• <key> (required): Configuration key to set or get; use `credential_store`.
• <value> (required): Credential store value: `auto`, `keyring`, or `shm`.
• --local: Save to local `.bk.yaml` instead of user config. The v3.47.0 source says `credential_store` is user-config-only, so this flag cannot be used for this key.
• Accepted values are `auto`, `keyring`, and `shm`.
• Precedence is `--credential-store` flag > environment > local config > user config > `auto`.
• Docs conflict: The release note says precedence includes local config. The v3.47.0 `bk config set` source marks `credential_store` as user-config-only and rejects `--local` for it.

FIRST-PARTY EVIDENCE

• https://github.com/buildkite/cli/releases/tag/v3.47.0
• https://github.com/buildkite/cli/pull/854
• https://buildkite.com/docs/platform/cli/reference/config
• https://github.com/buildkite/cli/blob/v3.47.0/cmd/config/set.go
• https://github.com/buildkite/cli/blob/v3.47.0/cmd/auth/login.go

Check the installed version and the source before using it. Entry JSON

Report a problem with this card