goharbor/harbor

Unable to replicate artifacts from Azure ACR

Open

#23,175 建立於 2026年4月27日

在 GitHub 查看
 (0 留言) (0 反應) (1 負責人)Go (28,490 star) (5,235 fork)batch import
help wanted

描述

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?

貢獻者指南

技術棧
goazure
領域
cloudbackend
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
4
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
over 1 week
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
blocked
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Go programmingHarbor replication conceptsAzure Container Registry API
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
15
研究方向
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.
Unable to replicate artifacts from Azure ACR · goharbor/harbor#23175 | Good First Issue