Project

Profile

Help

Task #7172

Delete a distribution along with a push repository

Added by lmjachky 2 months ago. Updated about 1 month ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Sprint/Milestone:
Start date:
Due date:
% Done:

100%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 79
Quarter:

Description

When a push repository is going to be deleted, a distribution that references this repository needs to be deleted as well.

Question remains: Should we DELETE a push repository via the pulp api? We should enable users to remove repos however there might be a race condition - a push to the repo X can happen while in the middle of push operation repo X can be deleted.


Related issues

Related to Container Support - Story #7013: Disallow update/partial_update of a push repo via pulp apiCLOSED - CURRENTRELEASE

<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

Associated revisions

Revision 9cf3853f View on GitHub
Added by mdellweg about 1 month ago

Delete push repositories with their distribution

Both entities can be used to trigger the deletion, and the deletions are coordinated in an atomic transaction.

fixes #7172 https://pulp.plan.io/issues/7172

Revision 9cf3853f View on GitHub
Added by mdellweg about 1 month ago

Delete push repositories with their distribution

Both entities can be used to trigger the deletion, and the deletions are coordinated in an atomic transaction.

fixes #7172 https://pulp.plan.io/issues/7172

History

#1 Updated by lmjachky 2 months ago

  • Related to Story #7013: Disallow update/partial_update of a push repo via pulp api added

#2 Updated by lmjachky 2 months ago

  • Description updated (diff)

#3 Updated by dkliban@redhat.com about 2 months ago

Yes, we should only allow users to delete Push repositories via Pulp's REST API. If the delete occurs while a user is pushing to this repository, at some point the user will start getting a 404 response from the registry API.

#4 Updated by ipanova@redhat.com about 2 months ago

  • Sprint set to Sprint 78

#5 Updated by mdellweg about 2 months ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to mdellweg

#6 Updated by pulpbot about 2 months ago

  • Status changed from ASSIGNED to POST

#7 Updated by rchan about 1 month ago

  • Sprint changed from Sprint 78 to Sprint 79

#8 Updated by mdellweg about 1 month ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100

#9 Updated by pulpbot about 1 month ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF