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

Pull Request (PR) description

puppet-lint flagged these lines

• 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.

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

• This project has a Contributor Code of Conduct: https://voxpupuli.org/coc/
• Please check that here is no existing issue or PR that addresses your problem.
• Our vulnerabilities reporting process is at https://voxpupuli.org/security/

-->

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
-->

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

• This project has a Contributor Code of Conduct: https://voxpupuli.org/coc/
• Please check that here is no existing issue or PR that addresses your problem.
• Our vulnerabilities reporting process is at https://voxpupuli.org/security/

-->

Pull Request (PR) description

Setup rsyslog so that if any $featurepackages are given rsyslog will
restart after those $featurepackages 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 $featurepackages in place.

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

• This project has a Contributor Code of Conduct: https://voxpupuli.org/coc/
• Please check that here is no existing issue or PR that addresses your problem.
• Our vulnerabilities reporting process is at https://voxpupuli.org/security/

-->

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" ]
...


modulesync 5.4.0

Redo of #151.

… resource

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

• This project has a Contributor Code of Conduct: https://voxpupuli.org/coc/
• Please check that here is no existing issue or PR that addresses your problem.
• Our vulnerabilities reporting process is at https://voxpupuli.org/security/

-->

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
-->