Comment 21 for bug 1778591

Adding this here so that my 2 cents from prior discussions elsewhere is recorded in this discussion.

In my mind, all that a consumer is to placement is a way to represent a batch of allocations created by a PUT (or POST in the multi case). That's it. It is a way for external clients of placement to determine who (in their system) is using what (quotas?), and to easily remove allocations when the consumer no longer needs them. When you delete the allocations for a consumer, the consumer is now meaningless, and should be deleted. Any GET referring to that consumer should return a 404.

In the case where a client's entity creates allocations, deletes them, and then creates new allocations, placement would create the consumer record, delete it, and re-create it again. Having a consumer record that doesn't refer to anything is meaningless, and messy.

Returning an empty dict for allocations is wrong. Just return 404.