How to make service to stop before changing the configuration, do configure and bring service up after instead of subscribing on configuration?
Is it possible to puppetize the flow described below, instead of standard puppet-way (package -> file ~> service)
- stop service, if configuration will be changed
- configure service config files
- start service
Ad.1: Don't wont to stop service if nothing changed