Service resource in prometheus::daemon does not depend on init_style dependent service description

[ghost]

Affected Puppet, Ruby, OS and module versions/distributions

• Puppet: 4.10
• Ruby: 2.1.9
• Distribution: CentOS 7
• Module version: v2.0.0

How to reproduce (e.g Puppet code you use)

 include prometheus::node_exporter

What are you seeing

Notice: /Stage[main]/Prometheus::Node_exporter/Prometheus::Daemon[node_exporter]/Group[prometheus]/ensure: created
Notice: /Stage[main]/Prometheus::Node_exporter/Prometheus::Daemon[node_exporter]/User[prometheus]/ensure: created
Notice: /Stage[main]/Prometheus::Node_exporter/Prometheus::Daemon[node_exporter]/Package[prometheus-node-exporter]/ensure: created
Error: Systemd start for node_exporter failed!
journalctl log for node_exporter:
-- No entries --

Error: /Stage[main]/Prometheus::Node_exporter/Prometheus::Daemon[node_exporter]/Service[node_exporter]/ensure: change from stopped to running failed: Systemd start for node_exporter journalctl log for node_exporter:
-- No entries --
Notice: /Stage[main]/Prometheus::Node_exporter/Prometheus::Daemon[node_exporter]/Systemd::Unit_file[node_exporter.service]/File[/etc/systemd/system/node_exporter.service]/ensure: defined content as '{md5}b94d9aa7e7c105276490a5eebf37560b'
...

Note that the service was started before the unit file was created, resulting in an error.

What behaviour did you expect instead

The service is only started after the unit file has been created.

[tuxmea]

systemd and sysv case statetments in daemon.pp (line 170-182) don't have the notify parameter which is present at all other $init_style cases