Background daemons of modules are not optional, so should not be treated like that in Puppet module

[dgoetz]

Expected Behavior

Background daemons of modules are not optional, so should not be treated like that in Puppet module by requiring an additional include.

Current Behavior

At the moment my profile has to look like this:

  class { 'icingaweb2::module::director':
     ...
   }

  include icingaweb2::module::director::service

Possible Solution

Add the include in the module class for existing module director, adjust #276 for vspheredb to also do so, do so when adding x509 and possible other modules in the future.

Context

Make configuration easier

Your Environment

• Module version (puppet module list): 3.0.1
• Puppet version (puppet -V): 6.13.0
• Operating System and version: CentOS 7