Clarify Tag History API token retrieval for private images (DOCS-136) - #3797
Merged
matthewhelmke merged 1 commit intoAug 18, 2026
Conversation
Lead with 'chainctl auth token --audience cgr.dev' as the direct way to get a registry-scoped token, and explain the --audience requirement (a default-audience token gets a 403). Keep the Docker credential helper and crane methods as alternatives. Fix a missing closing quote in the crane example. Refs DOCS-136. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
✅ Deploy Preview for ornate-narwhal-088216 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
matthewhelmke
marked this pull request as ready for review
August 18, 2026 17:34
s-stumbo
approved these changes
Aug 18, 2026
matthewhelmke
deleted the
matthewhelmke/docs-136-clarify-api-token-retrieval
branch
August 18, 2026 19:14
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this changes
Adds
chainctl auth token --audience cgr.devas the direct way to get a Tag History API token for private images, and explains why the--audience cgr.devflag is required. Keeps the Docker credential-helper andcranemethods as alternatives. Also fixes a missing closing quote in the existingcraneexample.Why
Customer feedback (DOCS-136): getting an API token "feels weird" — the docs route you through
configure-dockerand the Docker credential helper just to call the API, and a plainchainctl auth tokendoesn't work. The token only needs thecgr.devaudience; the credential-helper step isn't required.How this was tested
Verified end-to-end on a private, self-managed GitLab test instance (local k3s), calling a private Tag History API URL with an assumed Chainguard identity:
chainctl auth token --audience cgr.devdocker-credential-cgr getchainctl auth token(default audience)Tested with chainctl 0.2.333 against the
chainguard.eduorg. The guidance is independent of which images GitLab itself runs on.Refs DOCS-136.
Created in collaboration with Claude Code running Opus 4.8 on 2026-08-18.