Pulp

The results of a delete are:

  {
        "exception": null,
        "task_type": "pulp.server.managers.content.orphan.delete_all_orphans",
        "_href": "/pulp/api/v2/tasks/f2b5b41e-3586-4a8d-a5c7-b991cc0546bc/",
        "task_id": "f2b5b41e-3586-4a8d-a5c7-b991cc0546bc",
        "tags": [
            "pulp:content_unit:orphans"
        ],
        "finish_time": "2015-09-24T14:46:48Z",
        "_ns": "task_status",
        "start_time": "2015-09-24T14:46:19Z",
        "traceback": null,
        "spawned_tasks": [

        ],
        "progress_report": {

        },
        "state": "finished",
        "worker_name": "celery",
        "result": null,
        "error": null,
        "_id": {
            "$oid": "56040cbb45f9a6f0bb04ee23"
        },
        "id": "56040cbb45cf5608eda06ec0"
    }

What I'm asking for would be some statistics that really could just be a simple count of the number of files deleted but could get more detailed beyond that.
*

I modified the body of the story to orient it toward reporting how many of each unit type was removed. That's a fairly straight-forward change. I was able to throw together a proof-of-concept that produced the sample output in the body above:

https://github.com/pulp/pulp/compare/2.10-dev...mhrivnak:1268?expand=1

Does that meet the need?

If we needed to report details about each unit removed, that could become difficult, because it might be a HUGE list. It could be a lot of data to render, a lot to transfer via HTTP, and way too much to show to a user. But most importantly, it could exceed mongo's document size. We'd need to either truncate the data set (ugly), or batch the work into multiple tasks (lots of work and an API change).

Either way, my thinking is that reporting details of each unit removed would be an order of magnitude more work and complexity that just reporting counts, and it could easily lose its value to the user by becoming an overwhelming amount of data.

Looking at the downstream bug, they're actually fine with just getting back the counts.

I tested @mhrivnak's patch and it worked flawlessly. Proceeding with the other items.

Added a pulp smash issue.
https://github.com/PulpQE/pulp-smash/issues/459