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

Repo Checks ( 24 of 42 successfull )
Metadata Valid
No translation
passed
Correct Puppet Version Range
Supported Puppet version range is %{PUPPET_SUPPORT_RANGE}
passed
With Puppet Version Range
Puppet version range is present in requirements in metadata.json
passed
With Operatingsystem Support
No translation
passed
Operatingsystems
No translation
passed
Supports Only Current Redhat
No translation
passed
Supports Latest Redhat
No translation
passed
Supports Only Current Amazon
No translation
passed
Supports Latest Amazon
No translation
failed
Supports Only Current Oraclelinux
No translation
passed
Supports Latest Oraclelinux
No translation
failed
Supports Only Current Scientific
No translation
passed
Supports Latest Scientific
No translation
failed
Supports Only Current Centos
No translation
passed
Supports Latest Centos
No translation
failed
Supports Only Current Cloudlinux
No translation
passed
Supports Latest Cloudlinux
No translation
failed
Supports Only Current Xenserver
No translation
passed
Supports Latest Xenserver
No translation
failed
Supports Only Current Ubuntu
No translation
failed
Supports Latest Ubuntu
No translation
failed
Supports Only Current Debian
No translation
failed
Supports Latest Debian
No translation
passed
Supports Only Current Virtuozzolinux
No translation
passed
Supports Latest Virtuozzolinux
No translation
failed
Supports Only Current Archlinux
No translation
failed
Supports Latest Archlinux
No translation
failed
Supports Only Current Gentoo
No translation
failed
Supports Latest Gentoo
No translation
failed
Supports Only Current Raspbian
No translation
passed
Supports Latest Raspbian
No translation
failed
Supports Only Current Windows
No translation
passed
Supports Latest Windows
No translation
failed
Supports Only Current Aix
No translation
passed
Supports Latest Aix
No translation
failed
In Modulesync Repo
Is listed as a module managed using modulesync_config
passed
Synced
Has a .msync.yml file
passed
Latest Modulesync
Has been synchronized with the latest tagged version of modulesync_config
failed
Has Modulesync
Is present in voxpupuli/modulesync_config/managed_modules.yml
passed
Released
Is in modulesync_config and in forge releases.
passed
Valid Sync File
If a (optional) sync file is present, it must not contain a `.travis.yml` entry.
passed
Reference Dot Md
The repository has a REFERENCE.md. It needs to be generated / puppet-strings documentation is missing.
passed

Open Pull Requests

getting latest puppet-agent in place of the old 4.4.5 for Windows

Pull Request (PR) description

Updating to latest instead of 4.4.5

Open PR in GitHub
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
-->

Open PR in GitHub
Fix $hostinterfaceitem to not be an Fqdn.
merge-conflicts
bug

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

Open PR in GitHub
Restrict api access

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

Open PR in GitHub
Duplicate: Add sensitive support

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

Open PR in GitHub
Adding additional parameters for FPM configuration.
enhancement
needs-tests

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

Open PR in GitHub
Avoid deprecated hiera_hash function

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.

Open PR in GitHub
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
-->

Open PR in GitHub
Bugfixes
merge-conflicts
tests-fail
backwards-incompatible

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!

-->

Pull Request (PR) description

<!--
Replace this comment with a description of your pull request.
-->

This Pull Request (PR) fixes the following issues

Fixes #340

Open PR in GitHub
Timescaledb

Pull Request (PR) description

Import the zabbix timescaledb schema with a boolean flag.

This Pull Request (PR) fixes the following issues

n/a

Open PR in GitHub
Add sensitive support

Pull Request (PR) description

Adds sensitive support for passwords

This Pull Request (PR) fixes the following issues

Fixes #440

Open PR in GitHub
Add `authcfg`, `role`, `user` and `usergroup` API providers
enhancement

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

Open PR in GitHub
new param to specify database import timeout
needs-tests
merge-conflicts

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

Open PR in GitHub
Bootstrap agent2 support
enhancement
  • Add param binary_location for specify zabbix agent binary (only for systemd)
  • Remove some parameters in zabbix agent configuration if it's zabbix agent2 package
    • LogRemoteCommands
    • StartAgents
    • MaxLinesPerSecond
    • AllowRoot
    • User
    • LoadModulePath

Pull Request (PR) description

This Pr bootstrap a support for zabbix-agent2
It's possible to use agent2 with this configration:

'agent_configfile_path' => '/etc/zabbix/zabbix_agent2.conf',
'include_dir' => '/etc/zabbix/zabbix_agent2.d',
'pidfile' => '/var/run/zabbix/zabbix_agentd2.pid',
'servicename' => 'zabbix-agent2',
'zabbix_package_agent' => 'zabbix-agent2',
'binary_location' => '/usr/sbin/zabbix_agent2',

I actually not test with windows kernel (but I need it in few month)

This Pull Request (PR) fixes the following issues

692

Open PR in GitHub
Add acceptance for zabbix::proxy class

Pull Request (PR) description

Add acceptance test for proxy installation

This Pull Request (PR) fixes the following issues

Open PR in GitHub
Fixed missing item when syncing templates

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

-->

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

Open PR in GitHub
Test docker_podman support in beaker
skip-changelog

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

Open PR in GitHub
Add Zabbix 6.4 to CI matrix
enhancement

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

Open PR in GitHub
Restarting agent if it get's upgraded

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.

Open PR in GitHub
WIP: Add authcfg, role, user and usergroup API providers

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

Open PR in GitHub