GitHub puppet-zabbix

75

75

107

Puppet module for creating and maintaining zabbix components with puppet.

We rely on those packages in most tests. To be able to run them
independently, we need to manage them in the helper.

Adds new zabbix server & proxy parameters for TLS connection to the database

Does not deploy the cafile - that is left as a manual task for now.

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

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

This PR extends test matrix for testing Zabbix on Centos 8 (Related to: #643)

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

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

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

<!--
Adding possibility to define db_schema in zabbix.conf.php template, because of some cases where it needed also in other database engines as postgresql for example.
-->

This Pull Request (PR) fixes the following issues

<!--
N/A
-->

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

Adds parameters to set non-default values for option StartPreprocessors in zabbixserver.conf for Zabbix Server (supported since 3.4) and zabbixproxy.conf for Zabbix Proxy (supported since 5.0)

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

I needed to be able to override this option in Foreman on my proxy due to the default being too low for my configuration.

This Pull Request (PR) fixes the following issues

n/a

Increase max versions of dependency modules to allow for use of updated puppetlabs releases.

Needs https://github.com/camptocamp/puppet-systemd/pull/182.

Currently only works for zabbix5 when setting zabbix::agent::zabbix_version: 5.0 through hiera. As I haven't messed with the zabbix_version logic.

If someone can give some context on how zabbix_version should be used, I can give that a crack. I'm currently confused why this variable is being handled the way it is. (The Params class seems to just set the version based on OS, with default being 3.4?) Or whether there's a better way to get this information. A puppet fact maybe?

Pull Request (PR) description

This Pull request implements three Features:

1. It adds a new parameter purge_templates to zabbixagent that controls if additional templates configured in the server for the zabbixhost resource should be deleted.
2. it implements psk authentication for zabbix_host resources
3. it fixes a problem with zabbix_host resources with only IPMI interfaces

I found no easy way to split these commits into three PRs. If you know how to do this I would highly appreciate this.

This Pull Request (PR) fixes the following issues

Adds new parameters to allow specifying custom paths for the SAML certificates utilized for the SAML authentication configuration added in Zabbix 5.0.

<!--
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 adds parameters for setting custom SAML certificate paths for the SAML authentication configuration introduced in Zabbix 5.0 based on the official documentation located here: https://www.zabbix.com/documentation/current/manual/web_interface/frontend_sections/administration/authentication#advanced_settings

This Pull Request (PR) fixes the following issues

n/a

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

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":
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 packages for version 5.0 and 5.2.

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

This PR updates the zabbixapi gem to latest supported version for the
used zabbix version.

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

Zabbix 5.0 and greater enable extended range of float values.

This is by default for new installations.
However, when upgrading existing installations, a manual database
upgrade patch must be applied

The $DB[DOUBLE_IEEE754] value must be set to true in zabbix.conf.php. Otherwise, the message "Database history tables upgraded: No" will continue to be displayed in the web frontend.

Resource: ENABLING EXTENDED RANGE OF NUMERIC (FLOAT) VALUES

This Pull Request (PR) fixes the following issues

Fixes #734

Pull Request (PR) description

zabbix::agent

• logtype param was not defined in zabbix::params, also had different type enforcement that other classes

zabbix::server

• logfile param had different type enforcement that other classes

zabbix::proxy

• proxy config caters for sslcertlocation and sslkeylocation but these were not passable as params
  • also standardized the naming to match other modules in template
• logtype had different type enforcement that other classes
• fixed template to not put done extra blank lines midconfig

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