Project

Profile

Help

Issue #8014

closed

Ensure that container-push repo endpoint is read-only

Added by ipanova@redhat.com over 3 years ago. Updated about 3 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 88
Quarter:

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.


Related issues

Related to Pulp - Story #8103: As a plugin writer, I have a read-only viewset for repository available in the plugin APICLOSED - CURRENTRELEASEttereshc

Actions
Has duplicate Container Support - Issue #7839: push repository can be created without a distributionCLOSED - DUPLICATEttereshcActions

Also available in: Atom PDF