As a user I want to purge individual orphan or list of orphans
http POST :24817/pulp/api/v3/orphans/ content_hrefs:= 
Enable a POST call to the orphans endpoint that would accept a list of
content_hrefs to purge.
- A task will be triggered and will call into
orphan_cleanup(). Instead of looking for all of the orphaned content across pulp , it would just instead work with the list if hrefs provided( in case the list of
timestamp_of_intereston the content will be honored and if there was specified a Content unit that is not an orphan - it will be ignored.
- Only content that has
version_memberships__isnull=Truewill be purged.
This adds a new endpoint
/pulp/api/v3/orphans/cleanup/. When called
POST and no parameters it is equivalent to calling
DELETE /pulp/api/v3/orphans/. Additionally the optional parameter
content_hrefs can be specified and must contain a list of content
content_hrefs is specified, only those content units will
be considered to be removed by orphan cleanup.
#6 Updated by email@example.com 3 months ago
Maybe a silly question, but why wouldn't a user want all orphans removed?
In case a user has installed more than one plugin and he wants to remove one specific rpm package( for example), all other content types, including the ones from the other plugins would be cleaned up as well. This outcome might be undesirable.
Please register to edit this issue