While cc1cee8e61ded5c63d1c1e633bee99b2ced5ea69 already formally dropped support for Puppet, the code was still present and Foreman Proxy supported it too. In Foreman Proxy 3.4 the old puppetca_puppet_cert provider is dropped, meaning this is dead code anyway.
The puppetca_http_api provider is ensured absent to clean up the config file.
For compatibility with Foreman Proxy < 3.4 the puppet_version version is set to 6.0. This forces the puppetca_http_api provider to be used and a static value means fewer service restarts. Foreman Proxy >= 3.4 ignores this setting altogether.
This gets rids of various top level parameters, which simplifies things.
No care is taken to clean up sudo entries. It is assumed users already upgraded to Puppet 6 in which case the module previously cleaned up the entries. The proper upgrade path is to upgrade to Puppet 6 using theforeman/foreman_proxy 22.x and only then upgrade the module to the latest version.
Added by Ewoud Kohl van Wijngaarden almost 2 years ago
Refs #35184 - Drop puppetca_http_api provider
While cc1cee8e61ded5c63d1c1e633bee99b2ced5ea69 already formally dropped
support for Puppet, the code was still present and Foreman Proxy
supported it too. In Foreman Proxy 3.4 the old puppetca_puppet_cert
provider is dropped, meaning this is dead code anyway.
The puppetca_http_api provider is ensured absent to clean up the config
file.
For compatibility with Foreman Proxy < 3.4 the puppet_version version is
set to 6.0. This forces the puppetca_http_api provider to be used and a
static value means fewer service restarts. Foreman Proxy >= 3.4 ignores
this setting altogether.
This gets rids of various top level parameters, which simplifies things.
No care is taken to clean up sudo entries. It is assumed users already
upgraded to Puppet 6 in which case the module previously cleaned up the
entries. The proper upgrade path is to upgrade to Puppet 6 using
theforeman/foreman_proxy 22.x and only then upgrade the module to the
latest version.