Repository navigation
fix(source): point to helm registry login when a registry asks for basic auth - #129
Merged
Merged
Conversation
|
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.



What
An OCI registry that asks for a username and password, with no credentials saved for it, now gets the same hint as a 401 or 403: "not found, or private and no credentials (for a private registry, run
helm registry login <host>)", followed by the original error.Why
When the registry answers 401 with
WWW-Authenticate: Basicand Helm has nothing for that host, ORAS stops with "basic credential not found". The message has no status code and no "denied" or "unauthorized", so it went out raw, without saying what to check.Type
Checklist
go test ./...)docs/, ordocs/clivia gendocs)