Pull Request (PR) description

Updating to latest instead of 4.4.5

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

By default, the api is open to everyone. I would like to restrict it to only the zabbix server.

I’m not sure if it should be included in this module like I suggest, or if I should manage my own apache config by disabling this module apache management manage_vhost => false in web.pp, but I think the changes are simple enough to include in this module

My suggestion in this PR allow to add restriction to the api like so:
puppet
class { 'zabbix::web' :
[...]
zabbix_api_access => [$facts['networking']['fqdn']],
}


This creates this location entry in apache config (or equivalent in apache 2.2):
apache
<Location "/api_jsonrpc.php" >
Require host zabbix.example.com
</Location>


This Pull Request (PR) fixes the following issues

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

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

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

<!--
When keeping the template options in sync, one option, the template linkage, was missing and could prevent the puppet run from being idempotent.
-->

This Pull Request (PR) fixes the following issues

<!--
None, just an improvement of my previous added option to keep templates in sync.
-->

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

Add acceptance test for proxy installation

This Pull Request (PR) fixes the following issues

Pull Request (PR) description

Adds a Puppet provider using the API for the following resources:

Zabbix Authconfig
Zabbix User
Zabbix Usergroup
Zabbix Roles

Need to write acceptance for new resources

based on #829

Pull Request (PR) description

Add Ubuntu 24.04 to supported OS

This Pull Request (PR) fixes the following issues

This Pull Request (PR) include

952

Those runners contain 4 cores / 16G ram. The default S runners only have 2 cores.

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

Pull Request (PR) description

This is a copy of #828, where @bdeferme do not have any more time to work on it. Here I tried to fix the tests.

This Pull Request (PR) fixes the following issues

Fixes #440
Fixes #950

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

Newer apt based distros have deprecated apt keys stored in /etc/apt/trusted.gpg: installing zabbix agent with this module will result in the following warning:

shell
root@ubuntu:~# apt update
Hit:1 http://archive.ubuntu.com/ubuntu jammy InRelease
Hit:2 http://security.ubuntu.com/ubuntu jammy-security InRelease
Hit:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:4 http://apt.puppet.com jammy InRelease
Hit:5 http://repo.zabbix.com/zabbix/6.0/ubuntu jammy InRelease
Hit:6 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
51 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: http://repo.zabbix.com/zabbix/6.0/ubuntu/dists/jammy/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
root@ubuntu:~#
root@ubuntu:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04 LTS
Release: 22.04
Codename: jammy
root@ubuntu:~#


AFAIK this started happening in Debian >= 12 and Ubuntu >= 22.04

Using apt::keyring instead of apt::key seems to silence the warning.

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

We'd like to use this Puppet module to deploy our Zabbix infrastructure but to fully configer it for our needs there are missing some parameters. Im not able to fully test my additions, so a code review and/or testing is recommended.

Following parameters where added

• Server:
  • StartHistoryPollers
  • TrendFunctionCacheSize
• Agent:
  • StatusPort
  • PersistentBufferPeriod
  • ControlSocket

This Pull Request (PR) fixes the following issues

n.a.

Pull Request (PR) description

Add the ability to remove the Zabbix agent from a system using the ensure parameter.

feat: add tests for new "ensure" parameter in zabbix::agent

Pull Request (PR) description

I recently upgraded all agents to the latest 6.4 version of zabbix, and stumbled into Zabbix having issues eg getting old agents not compatible with new items from 6.4. I figured out that the upgrade of the agent-package did upgrade the agent, but it did not restart them, which left the old agent running. This had me to restart all agents manually. This fix will restart the agent if it get's upgraded.

Pull Request (PR) description

To not reveal Secrets, accept Datatype Sensitive. Render Templates as sensitive Content, if Secrets were given as Sensitive.

This Pull Request (PR) fixes the following issues

Fixes #950

Addendum

@teluq-pbrideau 2022-12 also made a PR #857, which has not been merged yet.

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

This PR enables 4 new server parameters for version >= 7
StartAgentPollers
StartHTTPAgentPollers
StartSNMPPollers
MaxConcurrentChecksPerPoller

Pull Request (PR) description

On Zabbix version 6.4 and newer there has been a change in the way
authentication is done. Using a bearer token would lead to issues with
authenticating using the API as the header did not seem the get passed to
the application.

This seems to have been known since the release of 6.4 and a bug report
is still open. But the bug report also already contained a
workaround/fix (https://support.zabbix.com/browse/ZBX-22952).

This Pull Request (PR) fixes the following issues

n/a

Pull Request (PR) description

Release 10.0.0 to:
* manage startup scripts
* Remove EOL and unsupported OSes
* Accept multiple TLSAccept options

This Pull Request (PR) fixes the following issues