goharbor/harbor

When can we do that Add aliyun acr ee As Supported Proxy-Cache Registry Source?

Open

#18,301 opened on Mar 3, 2023

View on GitHub
 (1 comment) (0 reactions) (1 assignee)Go (28,490 stars) (5,235 forks)batch import
area/proxy-cachehelp wantedkind/requirement

Description

Is your feature request related to a problem? Please describe. We want to use aliyun acr ee as the proxy image warehouse, but it doesn't seem to support it at present。

Describe the solution you'd like Add aliyun acr ee image library

Contributor guide

Tech stack
godockerkubernetes
Domain
backenddevopscloud
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 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.
needs investigation
Prerequisites
Go programmingDocker registry conceptsHarbor architectureproxy cache feature
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
The issue requests adding Aliyun ACR EE as a supported proxy cache registry source. The contributor should examine existing registry source implementations in the Harbor codebase (e.g., under src/pkg/reg/) to understand the pattern. They need to implement the necessary types and logic to support Aliyun ACR EE's authentication and API. The issue has an assignee, so check for any existing work or branch. Query maintainers for acceptance criteria and design details.
When can we do that Add aliyun acr ee As Supported Proxy-Cache Registry Source? · goharbor/harbor#18301 | Good First Issue