bk cache registry commands manage cluster cache registries
Introduced 2026-09-29 · score 0.98
HOW TO USE IT
When you need to manage a cluster cache registry, use `bk cache registry list|view|create|update|delete` with the cluster UUID and, for member commands, the registry UUID. Supply policy with `--policy-file`; use `-` for stdin, and use update clear flags to clear metadata or policy explicitly.
bk cache registry list <cluster-uuid> --limit 200bk cache registry create <cluster-uuid> --name "<name>" --policy-file <policy.yml>bk cache registry update <cluster-uuid> <registry-uuid> --clear-description --clear-policyWHY THIS HELPS
Manage cluster cache registries from a coding agent's terminal workflow.
BEFORE THIS CHANGE
Manage cache registries through the REST API or UI.
REQUIREMENTS AND LIMITATIONS
- Version: v3.59.0
- <cluster-uuid> (required): Cluster UUID; the target cluster for list/create, or the registry's cluster for view/update/delete.
- <registry-uuid> (required): Registry UUID to view, update, or delete.
- --name (required): Registry name on create; new name on update. Renaming regenerates the slug.
- --policy-file: YAML or JSON policy file path, or `-` to read stdin. Policy input must be an object; the CLI normalizes it to JSON.
- --description: Registry description on create or new description on update.
- --emoji: Registry emoji on create or new emoji on update.
- --color: Registry color on create or new color on update.
- --clear-description: Clear the registry description.
- --clear-emoji: Clear the registry emoji.
- --clear-color: Clear the registry color.
- --clear-policy: Clear policy, denying all cache saves and restores.
- --limit: Maximum registries returned by list; default 100.
- --per-page: Registries per page in list; default 30.
- --output: Output format: `json`, `yaml`, or `text`.
- policy.save: Policy section defining cache save scopes.
- policy.restore: Policy section defining cache restore scopes.
- policy.rules: Policy rules controlling actions such as save and restore.
- Prerequisite: Configure `bk` with an API access token for the target organization.
- Prerequisite: Registry operations require permission to manage the cluster. The API documentation specifies `read_clusters` for listing/getting and `write_clusters` for create/update/delete; deletion also requires permission to destroy the registry.
- Policy input accepts YAML or JSON files, or stdin, and must have an object root.
- Deletion is confirmed as a destructive action.
FIRST-PARTY EVIDENCE
- https://github.com/buildkite/cli/releases/tag/v3.59.0
- https://github.com/buildkite/cli/pull/1008
- https://buildkite.com/docs/platform/cli/reference/cache
- https://buildkite.com/docs/apis/rest-api/clusters/cache-registries
- https://buildkite.com/docs/platform/cli/configuration
Check the installed version and the source before using it. Entry JSON