With the defined pillar the salt-minion is not managed by the formulas (I choose to managed it thanks to supervisord)
But when a change is detection in /etc/salt/minion.d, the formula trigger the cmd.run state that runs service.restart
This should happened only if minion_service_details specify that it's managed by the formulas
Steps to reproduce the bug
Define upper pillar and make a change into the minion pillar (add a grains 4 example)
Your setup
Formula commit hash / release tag
73a082decb4a45f197c306afbcb55641f8d0f1b2
Versions reports (master & minion)
Pillar / config used
Bug details
Describe the bug
With the defined pillar the salt-minion is not managed by the formulas (I choose to managed it thanks to supervisord) But when a change is detection in /etc/salt/minion.d, the formula trigger the cmd.run state that runs service.restart This should happened only if minion_service_details specify that it's managed by the formulas
Steps to reproduce the bug
Define upper pillar and make a change into the minion pillar (add a grains 4 example)
Expected behaviour
state-minion > cmd.run should not triggers
Attempts to fix the bug
Fix attempt by extending the salt-minion job with