Metadata Valid
No translation
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?
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.
This pull request fixes a couple of issues I came across regarding passwords with special characters not being handled correctly.
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?
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
-->
This pull request adds option to specify interface type in agent.pp, so you can create an agent that is purely SNMP/JMX/IPMI.
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
<!--
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 PR extends test matrix for testing Zabbix on Centos 8 (Related to: #643)
<!--
Thank you for contributing to this project!
-->
zabbixapi 4.0.0 doesn't support Zabbix 4.2.
<!--
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
-->
<!--
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
-->
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
-->
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 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.