acr icon indicating copy to clipboard operation
acr copied to clipboard

How to get the sync-status of connected registry instances

Open fgheysels opened this issue 3 years ago • 4 comments

We're using the connected-registry feature to synchronize on-prem container -registries that are installed on vessels with the 'master' Azure Container Registry.

It would be nice if we could have an indication of the sync-status of our connected-registry instance so that we know which instances are completely in-sync with the master ACR and which are not yet completely synchronized.

fgheysels avatar Dec 13 '21 13:12 fgheysels

Hi @fgheysels, we do have the functionality deployed on the cloud side. However, we are still working on providing updates to the CLI that will make it easy to set up notifications for certain repositories.

One additional prerequisite for setting up notifications is to upgrade the connected registry module to version 0.6.0.

Until the CLI is available, there is a workaround that will require you to make a REST call to the ACR to set up the notification. You can make a PATCH call with the following payload to set up notifications:

{
    "properties": {
        "syncProperties": {
            "tokenId": "/subscriptions/[your_subscription_id]/resourceGroups/[your_resource_group]/providers/Microsoft.ContainerRegistry/registries/[your_registry]/tokens/[your_sync_token]",
            "schedule": "* * * * *",
            "messageTtl": "P2D",
            "syncWindow": null
        },
        "logging": {
            "logLevel": "Debug",
            "auditLogStatus": "Disabled"
        },
        "notificationsList": ["hello-world:*:*", "your_registry:*:*"] 
    }
}

The notificationsList property determines for which repositories you will receive notifications.

Please let us know if you have any other questions.

toddysm avatar Dec 24 '21 22:12 toddysm

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

github-actions[bot] avatar Nov 11 '23 01:11 github-actions[bot]

I was wondering if there are any updates on this :)

fgheysels avatar Nov 13 '23 16:11 fgheysels

@toddysm @leodewang one option is to move the issue to a milestone.

sajayantony avatar Jan 03 '24 21:01 sajayantony