goharbor/harbor

Support sonatype nexus as registry provider

Open

#15,422 opened on Aug 13, 2021

View on GitHub
 (12 comments) (0 reactions) (2 assignees)Go (28,490 stars) (5,235 forks)batch import
help wantedkind/requirementreplication/adapters

Description

It would be usefull to have support for sonatype Nexus as a resgitry provider.

Actually i'am not able to support the community with code but hopefully i can test proposed implementaion.

Versions: Please specify the versions of following systems.

  • harbor version: [Version v2.2.2-56d7937f]

Contributor guide

Tech stack
gorest api
Domain
backendinfrastructureapi
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
basic Go knowledgeunderstanding of container registriesfamiliarity with Harbor architecture
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Examine existing registry provider implementations in Harbor (e.g., in the 'src/registry' directory) to understand the required interface and patterns. Study the Sonatype Nexus REST API documentation for repository management, focusing on the operations needed for pushing and pulling container images. Review the issue comments and any linked discussions for additional context or requirements. Implement the new provider following the established pattern, integrating it into Harbor's registry provider framework.
Support sonatype nexus as registry provider · goharbor/harbor#15422 | Good First Issue