When `db_manage` and `db_manage_rake` are both set to `false`, there are no resources in `Class['foreman::database']` that get refreshed when configuration changes. As a result, `Class['foreman::service']` doesn't get notified and foreman isn't restarted.
This commit adds an explicit relationship between `Class['foreman::config']` and `Class['foreman::service']`.
Added by Alex Fisher over 7 years ago
Fix changes to config not restarting service
When `db_manage` and `db_manage_rake` are both set to `false`,
there are no resources in `Class['foreman::database']` that get
refreshed when configuration changes. As a result,
`Class['foreman::service']` doesn't get notified and foreman isn't
restarted.
This commit adds an explicit relationship between
`Class['foreman::config']` and `Class['foreman::service']`.
Fixes GH-502