Document registry usage and limitations - #132
Merged
alicefr merged 1 commit intoSep 11, 2026
Merged
Conversation
Collaborator
Author
Explain how the standard and authenticated endpoints share storage, how to configure credentials, and how their lifecycle differs. This gives users a complete workflow for testing protected image pulls without changing the unauthenticated development path. Closes: bootc-dev#129 Assisted-by: AI Signed-off-by: HarshwardhanPatil07 <harshpat@redhat.com>
HarshwardhanPatil07
force-pushed
the
docs-129-registry-usage
branch
from
September 7, 2026 11:29
b8c28c2 to
fcb94b4
Compare
Collaborator
Author
|
rebase |
6 tasks
alicefr
approved these changes
Sep 11, 2026
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
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.
Doc: Explains how the standard and authenticated endpoints share storage, how to configure credentials, and how their lifecycle differs. This gives users a complete workflow for testing protected image pulls without changing the unauthenticated development path.
Closes: #129
ref: #112
Assisted-by: AI