-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
First pass at rewriting the tokens/API section. #1732
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Max Allan <[email protected]>
Signed-off-by: Max Allan <[email protected]>
Signed-off-by: Max Allan <[email protected]>
✅ Deploy Preview for ornate-narwhal-088216 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, minor suggestions.
``` | ||
|
||
To make sure your token is set, you can run the following command: | ||
You may use the `crane` tool to get your token instead: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
``` | ||
Where `ORGANIZATION_NAME` is the name of your organization, for example: `company.com`, `IMAGE_NAME` is the name of the image, for example: `chainguard-base` (Note: the image name specified here does not need to be the same image you pass to the API later! But it needs to be a valid image from your registry.) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A little confusing.
Maybe:
Replace
ORGANIZATION_NAME
andIMAGE_NAME
as required. For example, if your organization isfoo.com
and you're interested in thechainguard-base
image:auth_header="$(crane auth token -H cgr.dev/foo.com/chainguard-base)"
I'm not sure if it's worth mentioning matching image names, just in case it changes.
There's still a section at the bottom on "enterprise images". I'm not sure if that also needs updated or if we can just delete. Let's not let it get in the way of this fix though. |
Signed-off-by: Max Allan [email protected]
Type of change
Documentation change
What should this PR do?
Fixes some incorrect content on how to get a token.
Why are we making this change?
The suggested method to get a token for private images was incorrect.
What are the acceptance criteria?
Review by docs team.
How should this PR be tested?
Try out the commands proposed.