Bug 713912 - [RFE] Repo delete web service and CLI should be able to pass the "delete packages" flag to the repo API
Summary: [RFE] Repo delete web service and CLI should be able to pass the "delete pack...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Pulp
Classification: Retired
Component: z_other
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Pradeep Kilambi
QA Contact: Preethi Thomas
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-16 18:39 UTC by Jay Dobies
Modified: 2012-07-11 20:15 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-07-11 20:15:36 UTC


Attachments (Terms of Use)

Description Jay Dobies 2011-06-16 18:39:14 UTC
When deleting a repo, the package bits on the server aren't removed, even if they are orphaned. To delete them then requires a WS call per package, which will add up in the case of deleting, say, an RHEL base channel.

I suspect (just my gut feeling) that the typical behavior in deleting a repo would be to reclaim that space as well, so we should provide a hook on repo delete that will have the Pulp server clean up the package bits (assuming they aren't being used by another repo) as part of the repo delete. That'd make the API a single call in that case.

Implementation Notes:
- The repo API already has an option for "keep_files", though I'm not 100% sure it works. It's set by default to False but the files aren't being deleted.

- Once that's resolved, we need to update the repo WS API to accept this as an optional flag in the DELETE call (we already do something similar for CDS unregister as a reference).

Comment 1 Todd Sanders 2011-06-21 17:11:22 UTC
Default behavior is working.  This RFE is about exposing the "keep files" attribute to the WS layer.

-Todd

Comment 2 Jay Dobies 2011-06-30 18:24:03 UTC
Removing the RHUI blocker tag from it, the default is fine for RHUI.

Comment 3 Jay Dobies 2012-07-11 20:15:36 UTC
Closing as this workflow has changed in v2 and this is no longer applicable.


Note You need to log in before you can comment on or make changes to this bug.