feat: support fetching Maven dependencies from artifact registry #1347
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.
This PR introduces support for using Artifact Registry as a remote Maven repository. Users can now fetch Maven dependencies from artifact registry with a URL with the
artifactregistry://
scheme.When we see a new Maven registry, if it's artifact registry, we try to create
google.DefaultClient
so requests can be authenticated. This automatically handles authentication using Application Default Credentials (ADC).After the client is created, when we try to make a request, if it's for artifact registry, we use this client; if the client is not available, we fall back to the default HTTP client. We also log
StatusForbidden
error for artifact registry.References: