Project

Profile

Help

Actions
Send by e-mail Copy link

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:
ttereshc
Sprint/Milestone:
2.3.0
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
Actions
Copy link
 #1

Updated by pulpbot over 3 years ago

  • Status changed from NEW to POST
Actions
Copy link
 #2

Updated by ipanova@redhat.com over 3 years ago

  • Status changed from POST to CLOSED - NOTABUG
Actions
Copy link
 #3

Updated by ipanova@redhat.com over 3 years ago

  • 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.

Actions
Copy link
 #4

Updated by ipanova@redhat.com over 3 years ago

  • Sprint/Milestone set to 2.3.0
Actions
Copy link
 #5

Updated by ipanova@redhat.com over 3 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to ttereshc
Actions
Copy link
 #6

Updated by ttereshc over 3 years ago

  • Related to Story #8103: As a plugin writer, I have a read-only viewset for repository available in the plugin API added
Actions
Copy link
 #7

Updated by ttereshc over 3 years ago

  • Has duplicate Issue #7839: push repository can be created without a distribution added
Actions
Copy link
 #8

Updated by ttereshc over 3 years ago

  • Subject changed from Disable POST for container-push repo endpoint to Ensure that container-push repo endpoint is read-only
  • Description updated (diff)
Actions
Copy link
 #9

Updated by ttereshc over 3 years ago

  • Sprint set to Sprint 88
Actions
Copy link
 #10

Updated by pulpbot over 3 years ago

  • Status changed from ASSIGNED to POST

Added by ttereshc over 3 years ago

Revision 5978f4ce | View on GitHub

Make push repositories REST API read-only

closes #8014 https://pulp.plan.io/issues/8014

Added by ttereshc over 3 years ago

Revision 5978f4ce | View on GitHub

Make push repositories REST API read-only

closes #8014 https://pulp.plan.io/issues/8014

Actions
Copy link
 #11

Updated by ttereshc over 3 years ago

  • Status changed from POST to MODIFIED
Actions
Copy link
 #12

Updated by pulpbot about 3 years ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
Send by e-mail Copy link

Also available in: Atom PDF