Fix failure to pull private packages due to URI scheme #2939
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.
Description of your changes
Fixes an issue with matching package pull secrets during registry authentication when auth data included a URI scheme (google/go-containerregistry#1299). Also, moves away from using the
LayerFromReader
function, which is now deprecated (due to issues with reading entire content into memory), but we opt to essentially replicate the previous behavior since we are currently only using it in tests and building packages with CLI (the latter of which we can optimize in the future, but have not here to keep the fix targeted).Fixes #2876
xref:
I have:
make reviewable
to ensure this PR is ready for review.backport release-x.y
labels to auto-backport this PR if necessary.How has this code been tested
Worked with @mcbenjemaa to verify that the issue with installing from artifact registry is now fixed, and also verified successful package install in my local environment.
Also validated that packages still build correctly with the
LayerFromOpener
change: