GitHub puppet-rsyslog
Puppet module for managing rsyslog

Repo Checks ( 18 of 26 successfull )
Metadata Valid
No translation
passed
Correct Puppet Version Range
Supported Puppet version range is %{PUPPET_SUPPORT_RANGE}
passed
With Puppet Version Range
Puppet version range is present in requirements in metadata.json
passed
With Operatingsystem Support
No translation
passed
Operatingsystems
No translation
passed
Supports Only Current Redhat
No translation
passed
Supports Latest Redhat
No translation
passed
Supports Only Current Centos
No translation
passed
Supports Latest Centos
No translation
failed
Supports Only Current Oraclelinux
No translation
passed
Supports Latest Oraclelinux
No translation
failed
Supports Only Current Scientific
No translation
passed
Supports Latest Scientific
No translation
failed
Supports Only Current Ubuntu
No translation
failed
Supports Latest Ubuntu
No translation
failed
Supports Only Current Debian
No translation
failed
Supports Latest Debian
No translation
failed
Supports Only Current Fedora
No translation
passed
Supports Latest Fedora
No translation
passed
In Modulesync Repo
Is listed as a module managed using modulesync_config
passed
Synced
Has a .msync.yml file
passed
Latest Modulesync
Has been synchronized with the latest tagged version of modulesync_config
failed
Has Modulesync
Is present in voxpupuli/modulesync_config/managed_modules.yml
passed
Released
Is in modulesync_config and in forge releases.
passed
Valid Sync File
If a (optional) sync file is present, it must not contain a `.travis.yml` entry.
passed
Reference Dot Md
The repository has a REFERENCE.md. It needs to be generated / puppet-strings documentation is missing.
passed

Open Pull Requests

Force apt::ppa before package
bug
tests-fail

Forces the configuration of the apt::ppa repository before the
installation of packages, so they will be installed in their correct
version.

Open PR in GitHub
Resolve puppet-lint notices

Pull Request (PR) description

puppet-lint flagged these lines

Open PR in GitHub
Add support for Debian 10 / CentOS 8
merge-conflicts
enhancement
tests-fail
Add Aix support
merge-conflicts
enhancement
needs-tests
tests-fail
  • Previously this module kinda supported AIX but had a few issues. This code adds better support and allows the user to control how the rsyslog package is installed and where from. AIX is still considered experimental but it works on several systems tested.
Open PR in GitHub
Add variables for conf_owner_name, conf_group_name and confdir_group_name for OS' that don't use root as group. owner_name for completeness
needs-tests
tests-fail

<!--
Thank you for contributing to this project!

-->

Pull Request (PR) description

<!--
Replace this comment with a description of your pull request.
-->

This Pull Request (PR) fixes the following issues

<!--
Replace this comment with the list of issues or n/a.
Use format:
Fixes #123
Fixes #124
-->

Open PR in GitHub
Add boolean variable to change behavior of multi-line actions in conf…

Added a boolean variable to control the multi-line behavior of the action module. If rsyslog::dontlinebreakactions == TRUE then all the options in the action will be on a single line.

This behavior might be necessary if you have CIS or STIG scans on your /etc/rsyslog.d configuration files that are looking for settings on a single line such as:

^\s*([^#]+\s+)?action\(([^#]+\s+)?\btarget="?[^#"]+"?\b

and

^\s*\*\.\*\s+@

These regexs will fail even if the configuration is correct but spans multiple lines.

Open PR in GitHub
try and validate config inside every potentially breaking concat/file…

… resource

<!--
Thank you for contributing to this project!

-->

Pull Request (PR) description

<!--
Replace this comment with a description of your pull request.
-->

This Pull Request (PR) fixes the following issues

<!--
Replace this comment with the list of issues or n/a.
Use format:
Fixes #123
Fixes #124
-->

Open PR in GitHub
Restart rsyslog if feature_packages are installed

<!--
Thank you for contributing to this project!

-->

Pull Request (PR) description

Setup rsyslog so that if any $featurepackages are given rsyslog will
restart after those $feature
packages are installed.

Forcing a restart of rsyslog after installation of any $featurepackages
are installed is important if you have an rsyslog config that is not
valid without the additional package from $feature
packages in place.

Open PR in GitHub
Allow usage of array in actions configs
merge-conflicts
tests-fail

<!--
Thank you for contributing to this project!

-->

Pull Request (PR) description

According to the doc (https://www.rsyslog.com/doc/v8-stable/configuration/modules/omrelp.html) omrelp tls permitted peers can be given as an array.
example:

tls.permittedPeer=["SHA1:...1", "SHA1:....2"]

This PR reuse the same logic present in inputs.epp for to deal with arrays.

This Pull Request (PR) fixes the following issues

Following puppet declaration :
```
class { 'rsyslog::config':
modules => {
'omrelp' => {},

},
actions => {

relp => {
type => 'omrelp',
config => {
target => 'logs.example.tld',
port => '2514',
tls => 'on',
'tls.mycert' => '/etc/ssl/certs/ssl-cert-snakeoil.pem',
'tls.myprivkey' =>'/etc/ssl/private/ssl-cert-snakeoil.key',
'tls.authmode' => 'fingerprint',
'tls.permittedpeer' =>['rsyslog_permittedpeers'],
}
},
}
```

produce the following rsyslog config :
```
module(load="omrelp")

relp

action(type="omrelp"
name="relp"
target="logs.example.tld"
port="2514"
tls="on"
tls.mycert="/etc/ssl/certs/ssl-cert-snakeoil.pem"
tls.myprivkey="/etc/ssl/private/ssl-cert-snakeoil.key"
tls.authmode="fingerprint"
tls.permittedpeer="[ 'rsyslog_permittedpeers' ]"
)
```

with the fix i have

...
tls.permittedpeer=[ "rsyslog_permittedpeers" ]
...

Open PR in GitHub