Geo: Sync Container Registry Rename/Move Origin Repository Events
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Context
Rename/Move Origin Repository requests Rename/Move a repository's origin path and all sub repositories under it. This is only available with registries backed by the metadata database and which have Redis enabled. This event is usually kicked off by renaming or moving repositories with container images in rails.
Problem
Currently, Geo does not sync Rename/Move Origin Repository requests from the primary registry to the secondary.
Without support for this in place, Geo users will not be able to take full advantage of all features enabled by the next generation container registry. With the completion of container-registry#1357 (closed) the container registry now emits rename events so we should be able to replicate the rename operation on secondary sites.
Additional Context of how Geo's handles current container registry push and delete notifications
There is an endpoint on the GitLab API that the notification will hit.
Typically for new notifications (e.g rename): we'll need to add this as an allowed event here.
And then in secondary Geo sites, do the rename as well. Here is what we do with a push or delete event-- we resync the container repository (which compares tags in both container repositories, pulls new ones to push into the secondary registry, and deletes excess ones in the secondary).