Open Stack

I'm looking at exactly the same problem in keystone, but considering a
slightly simpler variation of your call, e.g.:

  GET /projects?deleted

  GET /projects/{deleted_project_id}?deleted

I'm very hesitant to go down this road though... at least in the case of
keystone, we couldn't reliably expect these calls to actually return
anything (e.g. we might be able to soft-delete in one driver but not in
another, or an admin could clean up deleted entities periodically, etc).


-Dolph


On Mon, Apr 29, 2013 at 2:39 PM, Andrew M <ramielrowe at gmail.com> wrote:

> Hello,
>
> I'm working on a project that is cataloging and verifying the
> notifications being emitted by Nova. One of the functions of this system is
> to pull data from an alternate data source when notifications may have been
> missed/dropped. I'm thinking of using the Nova API as this source, but I've
> run into an issue. Currently the Nova API returns 404's on shows of deleted
> instances even if there is data in the database (thanks to soft-deletes).
>
> I'm wondering what the reason was for this behavior and would it be a good
> idea to perhaps return that data if a query param is set (something like
> 'show_deleted=true').
>
>
> --Andrew
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130429/edc1af89/attachment.html>