Story #1307
closed
As a user, I want to remotely unregister a consmer.
0%
Description
The current behavior of invoking the Consumer.unregistered() RMI on the agent when a consumer is deleted using API/pulp-admin is not the correct behavior. Instead, the registration status and associated artifacts (key, certificate) should solely be managed by pulp-consumer and that we discontinue invoking Consumer.unregistered() in the agent when a consumer is deleted.
If users really want to remotely unregister a consumer, I think we should support a new API pulp/consumers/<id>/actions/unregister/ that effectively does a
pulp-consumer unregister
remotely through the agent.
The suggested change untangles two very different use cases and provides a better separation of concerns.
This does not impact satellite. In fact, satellite sends a notify-agent: False to prevent Pulp from invoking the Consumer.unregistered() because katello-agent does not support it. In satellite, subscription manager solely manages registration status and artifacts on content hosts.
.