GitHub puppet-zabbix
75
75
100
Puppet module for creating and maintaining zabbix components with puppet.

Metadata Valid
No translation
Correct Puppet Version Range
Supported Puppet version range is %{PUPPET_VERSION_RANGE}
With Puppet Version Range
Puppet version range is present in requirements in metadata.json
With Operatingsystem Support
No translation
Supports Only Current Centos
No translation
Supports Latest Centos
No translation
Supports Only Current Ubuntu
No translation
Supports Latest Ubuntu
No translation
Supports Only Current Debian
No translation
Supports Latest Debian
No translation
In Modulesync Repo
No translation
In Plumbing
Is in plumbing
Has Secrets
Has a .sync.yml file
Synced
Has a .msync.yml file
Latest Modulesync
No translation
Has Modulesync
Is present in voxpupuli/modulesync_config/managed_modules.yml
Released
Is in modulesync_config and in forge releases.
Reference Dot Md
The repository has a REFERENCE.md. It needs to be generated / puppet-strings documentation is missing.

Open Pull Requests

Zabbix5 agent: allowkey, denykey params
needs-tests

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?

zabbix5: dbtls support
needs-tests

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.

Allow special characters in zabbixapi zabbix_pass & postgresql database_password
enhancement
needs-work
tests-fail

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
zabbix5: Allow DB creation

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?

Update zabbixapi gem to latest versions
tests-fail

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

<!--
Thank you for contributing to this project!

-->

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

Add option to specify type of interface in agent class

Pull Request (PR) description

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 database creation on zabbix version 5.x
enhancement

Pull Request (PR) description

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.

This Pull Request (PR) fixes the following issues

Zabbix database creation on version 5.x

opsgenie integration plugin needs ProtectHome = no
enhancement
needs-work

<!--
Thank you for contributing to this project!

-->

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

Extend test matrix to use CentOS 8
needs-work

Pull Request (PR) description

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

Upgrade zabbixapi package for Zabbix 4.2 support
bug
needs-feedback
needs-rebase
tests-fail

<!--
Thank you for contributing to this project!

-->

Pull Request (PR) description

zabbixapi 4.0.0 doesn't support Zabbix 4.2.

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

adding possibility to define db_schema in zabbix.conf.php template
enhancement
merge-conflicts
needs-tests

<!--
Thank you for contributing to this project!

-->

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 is a test PR
merge-conflicts

<!--
Thank you for contributing to this project!

-->

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

please mdlinter in README.md
docs

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

<!--
Thank you for contributing to this project!

-->

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

new param to specify database import timeout
needs-tests

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

Purging of Templates flag, IPMI Interface support, PSK Authentication
enhancement
needs-work
tests-fail

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