Skip to content

Container image virtual registry: manage APIs (registries and upstreams)

🗒️ Problem statement

In virtual registries, we usually have two set of APIs:

  1. APIs to manage the virtual registry objects. This issue deals with this part.
  2. APIs for the clients, $ docker, so that they can pull files through the virtual registry.

NOTE:

1️⃣ Registries

Route Notes
GET /groups/:id/-/virtual_registries/containers/registries List virtual registries for the given top level group
POST /groups/:id/-/virtual_registries/containers/registries Create a new virtual registry
GET /virtual_registries/containers/registries/:id Get the details of the virtual registry
PATCH /virtual_registries/containers/registries/:id Update a virtual registry
DELETE /virtual_registries/containers/registries/:id Delete a virtual registry

2️⃣ Upstreams

Route Notes
GET /virtual_registries/containers/registries/:id/upstreams Get the upstreams of a given registry
POST /virtual_registries/containers/registries/:id/upstreams Create an upstream for a given registry
GET /virtual_registries/containers/upstreams/:id Get the upstream details
PATCH /virtual_registries/containers/upstreams/:id Update the upstream details
DELETE /virtual_registries/containers/upstreams/:id Delete an upstream

🔮 Other considerations

Use a feature flag

🛠️ Implementation plan

Edited by Adie (she/her)