Page Comparison

...

As we were working through issues regarding

...

Our component modules will be patterned after the Puppet Labs suggested layout du jour. SIMP  SIMP-specific additions are in bold below.

• module/manifests/
  • init.pp 
  • params.pp
  • install.pp
  • config.pp
  • service.pp
  • config/firewall.pp
  • config/logging.pp
  • config/audit.pp
  • config/selinux.pp (this one may just have to be mixed in at times, however, any boolean flipping should probably be done here)
  • config/pkicerts.pp
  • config/tcpwrappers.pp
    

Each of these items in bold must adhere to the following:

1. They must be disabled by default
2. They must be name-based where the Boolean true and the Stringsimp String 'simp' amount to the same action (e.g., the Trevorian type "Stroolean")
3. They must allow for an ENC or Hiera or straight parameter, since we want maximum module uptake where possible

   1. This will look something like the following

      $enable$manage_firewall = defined($::enablemanage_firewall) ? $::enablemanage_firewall : hiera('enablemanage_firewall',false)

      1. Yes, this does mean that these features are disabled by default in the modules. However, they NOTE: the management defaults will be "false" as a safety consideration to Forge users who might try any SIMP module ala carte. However, these parameters will be enabled by default in simp-core, so we're ensuring maximum safety for downstream users.
      2. Can QUESTION: Should we make this defined->hiera->default logic a function in simplib? Is that too much trouble/obfuscation?

...