Skip to content

docs: describe registry_blob and registry_tag backend options - #691

Open
Rohit-Singh-01 wants to merge 1 commit into
uber:masterfrom
Rohit-Singh-01:patch-1
Open

Rohit-Singh-01 wants to merge 1 commit into
uber:masterfrom
Rohit-Singh-01:patch-1

Conversation

@Rohit-Singh-01

Copy link
Copy Markdown
Contributor

Related to #268 (does not close it).

The "Read-Only Registry Backend" section of docs/CONFIGURATION.md only showed a local-testing example. This adds a short explanation of the two registry backends, written from lib/backend/registrybackend:

  • registry_blob and registry_tag: which registry endpoints each one calls, and that both are read-only.
  • Shared options: address, timeout (default 60s), security.tls.client, security.basic, security.credsStore, security.enableHTTPFallback.
  • When authentication is attempted.

Docs only, 16 added lines, nothing removed. I read the code to check each statement. I did not cover the multiple-registries question from #268 (the gcr/.* namespace case), since I am not sure what behavior is intended there. Happy to adjust anything.

Add details about read-only registry backends and their options.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant