Unable to replicate artifacts from Azure ACR

[Cavaler]

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?

[mg1986jp]

The Azure ACR adapter in Harbor only registers image as a supported resource type, not artifact. You can see it in src/pkg/reg/adapter/azurecr/adapter.go — the Info() method returns:

SupportedResourceTypes: []string{
    model.ResourceTypeImage,
},

Compare this to the native adapter which supports both image and artifact. So when you try to replicate non-image artifacts (Helm charts, CNAB bundles, etc.) from ACR, Harbor skips them because the adapter doesn't advertise support for the artifact type.

As for why it's not documented — the ACR adapter was contributed as a community PR and the resource type limitation wasn't called out. Most ACR users replicate container images, so it probably went unnoticed.

Workaround: use the generic Docker registry adapter instead of the ACR-specific one. When creating the replication endpoint in Harbor, select "Docker Registry" as the provider instead of "Azure ACR". You'll need to provide a service principal or admin credentials manually, but the generic adapter supports artifact type replication since it uses the standard OCI distribution API.

The endpoint config would be:

• Provider: Docker Registry
• Endpoint URL: https://<your-registry>.azurecr.io
• Access ID: service principal app ID (or admin username)
• Access Secret: service principal password (or admin password)

If you need the ACR adapter to natively support artifacts, it'd be a small PR — just adding model.ResourceTypeArtifact to the SupportedResourceTypes slice and ensuring the adapter implements the ArtifactRegistry interface methods properly. The adapter already implements adp.ArtifactRegistry (line 63), so it might just be a missing registration.