Issue #8014
closed
Ensure that container-push repo endpoint is read-only
Status:
CLOSED - CURRENTRELEASE
Description
It is possible to create and delete push repositories using API.
It doesn't make sense, it doesn't benefit users in any way, it only potentially creates problems and adds complexity to the code and future RBAC.
Push repositories are automatically created during docker/podman push as a part of distribution creation.
Push repositories are automatically removed when their distributions are removed.
- Status changed from NEW to POST
- Status changed from POST to CLOSED - NOTABUG
- Status changed from CLOSED - NOTABUG to NEW
I am re-opening this bug. Users not should be able to create push repos via api. A distribution should be created instead and if needed assign needed permissions ahead of push operation. Push-repo will be created only during 'podman push' operation or alongside with the distribution creation.
- Sprint/Milestone set to 2.3.0
- Status changed from NEW to ASSIGNED
- Assignee set to ttereshc
- Related to Story #8103: As a plugin writer, I have a read-only viewset for repository available in the plugin API added
- Has duplicate Issue #7839: push repository can be created without a distribution added
- Subject changed from Disable POST for container-push repo endpoint to Ensure that container-push repo endpoint is read-only
- Description updated (diff)
- Status changed from ASSIGNED to POST
- Status changed from POST to MODIFIED
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Also available in: Atom
PDF
.
Make push repositories REST API read-only
closes #8014 https://pulp.plan.io/issues/8014