I'd really like to be able to define a top-level purge of supervisor.d resources, a la the puppetlabs-firewall module. We run a substantial number of processes that are to be run from a single location only for automated services without queueing (e.g. mass mails), so every class including such processes needs to include a boolean for ensure to make sure that if we switch around our master server duplicate processes on other machines are eliminated. Supervisord is a purely Puppet-managed process, so there's no real case in which
I'd expect this to be an entry in params defaulting to false that when set true purges /etc/supervisor.d of unknown resources and issues a supervisorctl stop.
Has this been discussed before, or do you have any reason to not implement this? I'd be happy to submit a PR but the work isn't worth it for our needs alone. Figured I'd touch base with you before doing the legwork.
Thanks very much for your work on this module!
I'd really like to be able to define a top-level purge of supervisor.d resources, a la the puppetlabs-firewall module. We run a substantial number of processes that are to be run from a single location only for automated services without queueing (e.g. mass mails), so every class including such processes needs to include a boolean for ensure to make sure that if we switch around our master server duplicate processes on other machines are eliminated. Supervisord is a purely Puppet-managed process, so there's no real case in which
I'd expect this to be an entry in params defaulting to false that when set true purges /etc/supervisor.d of unknown resources and issues a supervisorctl stop.
Has this been discussed before, or do you have any reason to not implement this? I'd be happy to submit a PR but the work isn't worth it for our needs alone. Figured I'd touch base with you before doing the legwork.