bk secret adds secret management commands
Introduced 2026-02-11 · score 0.96
HOW TO USE IT
When managing Buildkite secrets, use `bk secret` with the cluster ID and the relevant `create`, `update`, `delete`, `list`, or `get` subcommand. For example, create with `--cluster-id`, `--key`, and `--value`; the value can be entered interactively when omitted.
bk secret create --cluster-id <cluster-id> --key <key> --value "<secret-value>"bk secret update --cluster-id <cluster-id> --secret-id <secret-id> --description "<description>"bk secret list --cluster-id <cluster-id>WHY THIS HELPS
Manage secrets while maintaining a Buildkite pipeline.
REQUIREMENTS AND LIMITATIONS
- Version: v3.24.0
- --cluster-id <cluster-id> (required): Cluster ID; the v3.24.0 create command requires it.
- --key <key> (required): Secret key name, such as MY_SECRET.
- --value <value>: Secret value. If omitted, the CLI prompts interactively; with `--no-input`, it is required.
- --description <description>: Description of the secret; on update, changes the description.
- --policy <policy>: Secret access policy in YAML format.
- --secret-id <secret-id> (required): Secret ID used by get, update, and delete.
- --update-value: Prompt to update the secret value.
- --output, -o <format>: Output format: json, yaml, or text.
- --cluster-uuid <uuid>: Current online reference uses this cluster selector; it differs from the v3.24.0 source's `--cluster-id`.
- Docs conflict: The current Buildkite CLI reference uses `--cluster-uuid`; v3.24.0 source uses `--cluster-id`. Use `--cluster-id` for the card's stated version.
FIRST-PARTY EVIDENCE
- https://github.com/buildkite/cli/releases/tag/v3.24.0
- https://github.com/buildkite/cli/pull/638
- https://github.com/buildkite/cli/blob/v3.24.0/cmd/secret/create.go
- https://github.com/buildkite/cli/tree/v3.24.0/cmd/secret
- https://buildkite.com/docs/platform/cli/reference/secret
Check the installed version and the source before using it. Entry JSON