Dependency proxy for Maven: the prefill option
🎈 The prefill option
This issue is for discussing the value of having a prefill option in the dependency proxy (for Maven) UI.
The idea is that we would have a drop down with popular Maven registry providers and the external url
field would be prefilled with a template that users can complete.
Example of templates that could be used:
{
"maven-central": "https://repo.maven.apache.org/maven2/",
"github": "https://maven.pkg.github.com/<org>/<repository>",
"artifactory": "https://<org>.jfrog.io/artifactory/<repository name>",
}
Downside: this could confuse users that the dependency proxy only works for those providers where in fact, it will work with any Maven registry that accepts basic auth as an authentication method.
🔭 The Plan
From the investigation:
- Database model for the dependency proxy settings (#410714 - closed).
- The Maven dependency proxy API: cache hit path (#410717 - closed).
- The Maven dependency proxy API: cache miss path (#410719 - closed).
- The dependency proxy API skeleton for Maven pac... (#410721 - closed).
- The dependency proxy settings GraphQL API (#410725 - closed).
- Dependency proxy for Maven: frontend changes (#410726 - closed).
- (Option) The frontend prefill option. (
👈 this issue) - Document the dependency proxy for Maven (#410731 - closed)
Edited by David Fernandez