...
- SIMP subsystems rely on environmental conventions that cannot be assumed to be present outside of SIMP.
- They are opt-in, so Forge users can use SIMP modules within non-SIMP infrastructures.
- A full SIMP ecosystem's hiera will enable each subsystem by default in
simp_def.yaml - IMPORTANT: These subsystem only manage SIMP-related resources and integrations for the module.
- Each module may naturally have its own way of configuring PKI, tcpwrappers, etc. That belongs within the conventional module structure.
- Examples: enabling SSL or TCP wrappers in a config file, setting SELinux contexts (for module resources
- QUESTION: are any of the SELinux contexts we use SIMP-specific? ANSWER: No),
- Each module may naturally have its own way of configuring PKI, tcpwrappers, etc. That belongs within the conventional module structure.
Standard Class Parameters in init.pp
...