feat: disable cobbler cache (#256)

- this is required to resolve issues with terraform deploying cobbler
  settings

Reviewed-on: https://git.query.consul/unkinben/puppet-prod/pulls/256

site/profiles/manifests/cobbler/config.pp

@@ -11,6 +11,7 @@ class profiles::cobbler::config {
   $service_cname = $profiles::cobbler::params::service_cname
   $next_server = $profiles::cobbler::params::next_server
   $server = $profiles::cobbler::params::server
+  $cache_enabled = $profiles::cobbler::params::cache_enabled
 
   # manage the cobbler settings file
   file { '/etc/cobbler/settings.yaml':

site/profiles/manifests/cobbler/params.pp

@@ -9,6 +9,7 @@ class profiles::cobbler::params (
   String  $next_server   = $::facts['networking']['ip'],
   Boolean $pxe_just_once = true,
   Boolean $is_cobbler_master = false,
+  Boolean $cache_enabled = false,
   Array   $packages = [
       'cobbler',
       'cobbler3.2-web',

site/profiles/templates/cobbler/settings.yaml.erb

@@ -59,7 +59,7 @@ build_reporting_ignorelist: []
 # use cases like writing out large numbers of records. There is a known issue with cache and remote XMLRPC API calls.
 # If you will use Cobbler with config management or infrastructure-as-code tools such as Terraform, it is recommended
 # to disable by setting to false.
-cache_enabled: true
+cache_enabled: <%= @cache_enabled %>
 
 # Cheetah-language autoinstall templates can import Python modules. While this is a useful feature, it is not safe to
 # allow them to import anything they want. This whitelists which modules can be imported through Cheetah. Users can