-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(datasource/maven): Add Artifact Registry support via Google ADC #24657
feat(datasource/maven): Add Artifact Registry support via Google ADC #24657
Conversation
@kvanzuijlen is this ready for review? |
Somehow it passes coverage. @zharinov is this possibly a bug in our sharded tests? |
I think the coverage check was skipped? |
Yes you're right - due to it being a draft PR |
… into maven-artifact-registry-support
Thank you so much for taking the time to review my PR @Churro |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please make sure getGoogleAuthToken()
also has its own test in util.spec.ts
.
Co-authored-by: Johannes Feichtner <343448+Churro@users.noreply.github.com>
🎉 This PR is included in version 37.20.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Changes
Adds Google Application Default Credentials (ADC)/Workload Identity support for Maven repositories
Context
This change makes configuring Artifact Registry support easier and makes use of best practices.
Documentation (please check one with an [x])
How I've tested my work (please select one)
@viceice My proposal for writing unit tests for this change is to add tests to the
downloadMavenXml
block and add a new block to specifically testdownloadArtifactRegistryProtocol
. Do you agree with this proposal?I have verified these changes via: