Container image virtual registry: manage APIs (cache entries)
🗒️ Problem statement
In virtual registries, we usually have two set of APIs:
- APIs to manage the virtual registry objects. This issue deals with this part.
- APIs for the clients,
$ docker, so that they can pull files through the virtual registry.
NOTE: Registries and upstreams API is handled in #548794 (closed). This issue is for cache entries.
Cache entries
| Route | Notes |
|---|---|
| GET /virtual_registries/containers/upstreams/:id/cache_entries | List all the cache entries of a given upstream |
| DELETE /virtual_registries/containers/cache_entries/*id | Delete a given cache entry |
🔮 Other considerations
Use a feature flag
🛠️ Implementation plan
- Container image virtual registry: database models (#548783 - closed) • Adie (she/her), Radamanthus Batnag • 18.5 • Needs attention
- Container image virtual registry: cache entry s... (#549103 - closed) • Radamanthus Batnag • 18.5 • On track
- Container image virtual registry: upstream serv... (#549104 - closed) • Adie (she/her) • 18.4
- Container image virtual registry: handle file r... (#549134 - closed) • Adie (she/her) • 18.6
- Container image virtual registry: manage APIs (... (#548794 - closed) • Adie (she/her) • 18.5 • On track
- Container image virtual registry: push/pull end... (#549131 - closed) • Radamanthus Batnag • 18.8 • At risk
- Container image virtual registry: performance r... (#549136) • Radamanthus Batnag • 18.10 • On track
- Container image virtual registry: documentation... (#549138 - closed) • Adie (she/her) • 18.6
- Container image virtual registry: additional fe... (#549470) • Unassigned • Backlog
Edited by 🤖 GitLab Bot 🤖