This is not correct. This changelog entry references the “Sensu API”,
and removing client from it. (sensu-cli client delete, etc) This is
not related to stopping the sensu-client service.
AFAIK the above feature is not being worked on, as it would violate
the principle of least surprise.
If you wanted to implement this feature locally, you could do
something like the equivalent of a “post-start” script in upstart that
runs “sensu-cli client delete” to delete the client.
At work we have a similar init script that runs a deregister on
runlevel 0 (halt).
On Fri, Jan 8, 2016 at 3:25 AM, Alex Leonhardt email@example.com wrote:
According to the update in 0.20.6
am I understanding correctly that
when sensu-client service is stopped on a host
and there are no outstanding “alerts” for that host
then the sensu-api service will remove the host from sensu
is this correct ?
If not, is the above “feature” still being worked on ? If so, is there a
github issue for it and a ETA for it (or a roadmap) ?