goharbor/harbor

Unable to replicate artifacts from Azure ACR

Closed

#23,175 opened on Apr 27, 2026

View on GitHubContributor guide
 (1 comment) (0 reactions) (1 assignee)Go (5,235 forks)batch import
help wanted

Repository metrics

Stars
 (28,490 stars)
PR merge metrics
 (Avg merge 8d 17h) (74 merged PRs in 30d)

Description

Discussed in https://github.com/goharbor/harbor/discussions/23162

Originally posted by Cavaler April 22, 2026 Replicating from Azure ACR seemingly supports only "image", not "artifact". I would like to know, why? And why isn't it documented?

And most importantly, is there a way to work around that?

Contributor guide

Research direction
Examine the replication flow code in Harbor, focusing on how artifact types are handled when pulling from Azure ACR. Identify where the filter for 'image' vs 'artifact' is applied and determine if adding support for artifacts requires changes in the adapter or registry interface.
Tech stack
godocker
Domain
backendcloudapi
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GoDockerHarbor replication knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40