Metadata Valid
No translation
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.
Have only tested with postgresql.
Duplicate of #694 - but there hasn't been any activity on that for 3 months. @bastelfreak Could you point me to the acceptance tests that need to be modified? (And is it possible to test these locally, or only through travis?)
On a side note: Looks like this logic can be simplified significantly if support for zabbix <3 is dropped. Looks like Zabbix themselves have dropped support for them, and only supports 3 onwards. Would you consider dropping support for zabbix versions <3?
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
This PR extends test matrix for testing Zabbix on Centos 8 (Related to: #643)
<!--
Thank you for contributing to this project!
-->
<!--
Replace this comment with a description of your pull request.
-->
<!--
Replace this comment with the list of issues or n/a.
Use format:
Fixes #123
Fixes #124
-->
<!--
Thank you for contributing to this project!
-->
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.
-->
<!--
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!
-->
<!--
Replace this comment with a description of your pull request.
-->
<!--
Replace this comment with the list of issues or n/a.
Use format:
Fixes #123
Fixes #124
-->
<!--
Thank you for contributing to this project!
-->
<!--
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.
-->
<!--
N/A
-->
This pull request fixes a couple of issues I came across regarding passwords with special characters not being handled correctly.
Zabbix 5.x is out. This means that the regex in the database creation files is no longer valid (it checks for v3/4). It needs to include version 5 as well.
Zabbix database creation on version 5.x
Changes the apache::vhost configuration to work with the changes in Zabbix 5.0 regarding minimum PHP version and CentOS 7 by utilizing the up-to-date package names for the official packages.
<!--
Thank you for contributing to this project!
-->
This PR makes changes to support the updated frontend configuration required as detailed in the official documentation: https://www.zabbix.com/documentation/current/manual/installation/frontend/frontend_on_rhel7
The test portion is kind of sketchy without re-writing the entire spec to test for specific values of zabbixversion, however, will hopefully work correctly if the default zabbixversion changes.
n/a
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!
-->
I needed to be able to override this option in Foreman on my proxy due to the default being too low for my configuration.
n/a
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?
This Pull request implements three Features:
purge_templates to zabbixagent that controls if additional templates configured in the server for the zabbixhost resource should be deleted.I found no easy way to split these commits into three PRs. If you know how to do this I would highly appreciate this.
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 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
n/a
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!
-->
<!--
Replace this comment with a description of your pull request.
-->
Fixes #340
This PR updates the zabbixapi gem to latest supported version for the
used zabbix version.
<!--
Thank you for contributing to this project!
-->
<!--
Replace this comment with a description of your pull request.
-->
<!--
Replace this comment with the list of issues or n/a.
Use format:
Fixes #123
Fixes #124
-->
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].
Fixes #725