goharbor/harbor

Unable to replicate artifacts from Azure ACR

Open

#23175 opened on Apr 27, 2026

View on GitHub
 (0 comments) (0 reactions) (1 assignee)Go (28,490 stars) (5,235 forks)batch import
help wanted

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

Tech stack
goazure
Domain
cloudbackend
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.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Go programmingHarbor replication conceptsAzure Container Registry API
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
Examine the replication implementation in Harbor, particularly the Azure ACR adapter (likely in src/pkg/replication/adapter/azurecr or similar). Review the discussion at https://github.com/goharbor/harbor/discussions/23162 for context. Understand how artifact types are handled during replication and why only 'image' is supported. Consider adding support for OCI artifacts other than images.