This pull request fixes a couple of issues I came across regarding passwords with special characters not being handled correctly.

1. Zabbixapi not accepting passwords with special characters (I'm not too familiar with ruby, but this fix works in my tests)
2. postgresql echo exec not handling passwords with special characters correctly

Zabbix now provides Ubuntu Focal deb packages for the arm64 architecture:
https://support.zabbix.com/browse/ZBXNEXT-5982

They can be found under a different URL than "usual", for example:
https://repo.zabbix.com/zabbix/5.2/ubuntu-arm64/

so the repo.pp manifest has to be adapted to refelct this.

Be careful: Right now, Zabbix only provides aarch64 packages for version 5.0 and higher.

this fixes:
MD001 Header levels should only increment by one level at a time

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

Pull Request (PR) description

As per #725 and the upstream documentation, zabbix::agent::hostinterfaceitem should not be an FQDN as it refers to a Zabbix item.

I did not set a type, to match the similar $hostmetadataitem. Let me know if I should instead set it to be something like Optional[String].

This Pull Request (PR) fixes the following issues

Fixes #725

• Add param binary_location for specify zabbix agent binary (only for systemd)
• Remove some parameters in zabbix agent configuration if it's zabbix agent2 package
  • LogRemoteCommands
  • StartAgents
  • MaxLinesPerSecond
  • AllowRoot
  • User
  • LoadModulePath

Pull Request (PR) description

This Pr bootstrap a support for zabbix-agent2
It's possible to use agent2 with this configration:

'agent_configfile_path' => '/etc/zabbix/zabbix_agent2.conf',
'include_dir' => '/etc/zabbix/zabbix_agent2.d',
'pidfile' => '/var/run/zabbix/zabbix_agentd2.pid',
'servicename' => 'zabbix-agent2',
'zabbix_package_agent' => 'zabbix-agent2',
'binary_location' => '/usr/sbin/zabbix_agent2',


I actually not test with windows kernel (but I need it in few month)

This Pull Request (PR) fixes the following issues

692

Pull Request (PR) description

The update_pgpass resource may fail when using strong ${database_password} that contain special characters such as & because the echoed string is not escaped. This Pull request adds ~~double quotes~~ shell_escape() (as suggested by @smortex).

This Pull Request (PR) fixes the following issues

• Fixes #830

modulesync 5.3.0

Pull Request (PR) description

This PR adds support for the 2 FPM configurations mentioned here that appear to resolve issues with FPM memory usage on RHEL/CentOS hosts.

This Pull Request (PR) fixes the following issues

No issues related to this PR

Pull Request (PR) description

Introduce module Hiera data with pre-defined merge behaviour for zabbix::userparameter::data.

This Pull Request (PR) fixes the following issues

Fixes #777

As of now, there are no spec tests for the newly introduced module Hiera hierarchy and merge behaviour. I've googled around a bit and could not find a solution to integrate into this module easily. Though if you have any examples where spec tests are already implemented for a voxpupuli project with static Hiera data, I'd be willing to try that myself.

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

For opsgenie integration plugins it is needed that on systemd enabled systems the setting "ProtectHome" is "no". The reason is that the integration plugin is tightly coupled in /home/opsgenie.

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

Update server.pp to allow setting 'startescalators' and 'sslcalocation_dir' variables
Update proxy.pp to correct spellings of 'unavailabledelay' and 'unreachabledelay' variables

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

Fixes #340

Pull Request (PR) description

Import the zabbix timescaledb schema with a boolean flag.

This Pull Request (PR) fixes the following issues

n/a

Pull Request (PR) description

Adds sensitive support for passwords

This Pull Request (PR) fixes the following issues

Fixes #440

Pull Request (PR) description

Adds a Puppet provider using the API for the following resources:
- Zabbix Authconfig
- Zabbix User
- Zabbix Usergroup
- Zabbix Roles

This Pull Request (PR) fixes the following issues

n/a

Configures a timeout param for the database import execs. The default timeout of 300 seconds causes database creation to fail on some systems. Have set default to 600, but haven't tested to determine the optimal value.

fixes #667

Pull Request (PR) description

On RHEL systems do not try to install the centos-release-scl package as its not present and fails it

I chose to specifically chose to exclude Red Hat rather than to only trigger when CentOS is detected, i am unclear if the scl release will install on other variants like Rocky or AlmaLinux or not - and figured it was safer to only deal with the specific use case - otherwise this could be changed if required

This Pull Request (PR) fixes the following issues

Fixes #823

Pull Request (PR) description

inspired from #700

I need to authenticate with certificate in my infrastructure, this PR allow to push the configuration to the zabbix server via «storeconfigs»

As stated in #700, there is an issue with setting the PSK through the API as PSK values are write only since zabbix 5.4. So I didn’t bother to dig deeper on this part, as I don’t require it in my infrastructure.

This Pull Request (PR) fixes the following issues