Affected Puppet, Ruby, OS and module versions/distributions
Puppet: any
Ruby: aby
Distribution: any
Module version: any
How to reproduce (e.g Puppet code you use)
Setup a unit file with systemd::manage_unit or directly with systemd::unit_file. Have some of the contents change.
What are you seeing
puppet-systemd will restart the service no matter what.
What behaviour did you expect instead
I'd expect to have the possibility to disable puppet-systemd restart the service(s) in question when the unit file changes (while still executing daemon-reload so systemd has the most recent version of the unit file loaded).
This is needed especially when touching multiple services per server across multiple servers. The on-disk unit files as well as systemd's view need to be updated, but no further action should be taken as this must be done outside of Puppet.
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
Setup a unit file with systemd::manage_unit or directly with systemd::unit_file. Have some of the contents change.
What are you seeing
puppet-systemd will restart the service no matter what.
What behaviour did you expect instead
I'd expect to have the possibility to disable puppet-systemd restart the service(s) in question when the unit file changes (while still executing daemon-reload so systemd has the most recent version of the unit file loaded).
This is needed especially when touching multiple services per server across multiple servers. The on-disk unit files as well as systemd's view need to be updated, but no further action should be taken as this must be done outside of Puppet.
Output log
Any additional information you'd like to impart