OP#501 adding variables and place holders for certs

This commit is contained in:
2026-03-15 14:49:49 +01:00
parent 80dcda911b
commit 502b028440
3 changed files with 7 additions and 4 deletions

View File

@@ -12,6 +12,7 @@
- [Dependencies](#dependencies)
- [Deployment](#deployment)
- [Managing Check Commands](#managing-check-commands)
- [managing TLS serts](#managing-tls-serts)
- [SELINUX](#selinux)
- [Known Problems](#known-problems)
- [Troubleshooting](#troubleshooting)
@@ -99,6 +100,8 @@ A: Sometimes the name of the check is different, like this:
It is very recommendable to define such commands directly within Puppet modules or profiles, so any node running the particular service controlled by the module will automatically get the required check commands defined as well, while nodes not running the service also do not contain the command check. The same then is true for Nagios checks, so you would have both the NRPE command definition and the Nagios check contained in Puppet modules or profiles to have it in one location.
## managing TLS serts
## SELINUX
All files and directories are configured with correct selinux context. If selinux is disabled, these contexts are ignored.

View File

@@ -1,3 +1,3 @@
<% unless $ne_ssl_cert_pem == undef -%>
<%= $ne_ssl_cert_pem %>
<% unless @ne_ssl_cert_pem.nil -%>
<%= @ne_ssl_cert_pem %>
<% end -%>

View File

@@ -1,3 +1,3 @@
<% unless $ne_ssl_privatekey_pem == undef -%>
<%= $ne_ssl_privatekey_pem %>
<% unless @ne_ssl_privatekey_pem.nil -%>
<%= @ne_ssl_privatekey_pem %>
<% end -%>