Actions
Story #6825
closedIntroduce a new repo type for the docker push usecase
Start date:
Due date:
% Done:
100%
Estimated time:
(Total: 0:00 h)
Platform Release:
Groomed:
Yes
Sprint Candidate:
No
Tags:
Sprint:
Sprint 76
Quarter:
Description
There will be 2 repo types: ContainerRepo and ContainerPushRepo. The gist is - repo created for docker push cannot be used for mirroring content and viceversa. Content curation will still be possible on both repo types
Push repo:
- Cannot be created/updated via Pulp API (https://pulp.plan.io/issues/7013)
- Will be created on demand by Registry API
- Can be used for push content from docker/podman client or via Docker Registry API
- Cannot be used for syncing content
- Artifacts cannot be removed via Pulp API, docker API can be used to manipulate content of a push repo
- Artifacts can be copied from a push repo to a container repo via Pulp API
- Artifacts cannot be copied into a push repo
- No rollback available, latest version is always served
Container Repo:
- Cannot be used for push content from docker/podman client or via Docker Registry API
- Can be used for syncing content
- Artifacts can be removed via Pulp API only
- Artifacts can be copied from a push repo to a container repo via Pulp API
- Artifacts can be copied from a container repo to a container repo via Pulp API
- Rollback availalbe, latest or specific repo version can be served
Related issues
Actions
Add ContainerPushRepository type
fixes #6825 https://pulp.plan.io/issues/6825