Foreman » Installer

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...

Fixes #16802 - enable hammer openscap plugin installation

fixes #17133 - add puppet::server::config (CA) dep to foreman::service

Anchor Service[httpd] inside foreman::service

Ensures that specifying a resource happens before foreman::service (e.g.
cert generation) will occur before the service is started.

The apache class is no longer run before foreman::config, only
foreman::service (as it contains the service too.)

Add Archlinux data to params and provider::params

allow foreman-cli package to be updated

Fix false "The system does not seem to be IPA-enrolled" result.

refs #16250 - mark advanced parameters

introduce db_managed_rake flag

This makes it possible to have the databases on an external server,
using db_manage=false, while still populating the database with the
required rake jobs.

closes GH-473

add plugin foreman_omaha