Story #2396
As a user, I can remove orphaned content and related artifacts by content type
Status:
NEW
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Description
Motivation¶
With upcoming content migration from Pulp 2 (which can be done by content type), it becomes important to have control which orphans to delete and avoid removing content which was recently migrated but hasn't been added to any repository yet.
Suggestion¶
Add type parameter to the orphan cleanup endpoint to filter what to delete:
$ http DELETE /pulp/api/v3/orphans/ type=file
Only artifacts related to the specified content type should be removed.
Related issues
History
#1
Updated by ttereshc about 4 years ago
- Related to Task #2380: Create a redmine task for each 2.y celery task to be converted to 3.0 added
#2
Updated by ttereshc about 4 years ago
- Tags Pulp 3 added
#3
Updated by fdobrovo about 4 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to fdobrovo
#4
Updated by fdobrovo about 4 years ago
- Status changed from ASSIGNED to NEW
- Assignee deleted (
fdobrovo)
#5
Updated by bmbouter over 1 year ago
- Tags deleted (
Pulp 3)
#6
Updated by ttereshc over 1 year ago
- Tracker changed from Task to Story
- Subject changed from Convert celery task content.orphan.delete_orphans_by_type to Pulp 3 to As a user, I can remove orphaned content and related artifacts by content type
- Description updated (diff)
#7
Updated by ttereshc over 1 year ago
- Description updated (diff)
Please register to edit this issue
.