Updating to latest instead of 4.4.5
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.
Refactoring to use structured $facts hash syntax in unit tests
Add unit tests to reach 100% resource coverage
This adds the optional parameter StatsAllowedIP to zabbix server and proxy.
The paramter has been supported since v4.2
n/a
This pull request fixes a couple of issues I came across regarding passwords with special characters not being handled correctly.
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", for example:
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 aarch64 packages for version 5.0 and higher.
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
-->
Add support for FreeBSD only for Zabbix Agent.
Tested on FreeBSD 13.1 with puppet 7.23
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)
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
The update_pgpass
resource may fail when using strong ${database_password}
that contain special characters such as &
because the echoed string is not escaped. This Pull request adds ~~double quotes~~ shell_escape()
(as suggested by @smortex).
fix: add documentation to satisfy linting
Fixes the following warnings that do pop up while linting:
[warn]: Missing documentation for Puppet type alias 'Zabbix::Historyics' at types/historyics.pp:1.
[warn]: Missing a description for Puppet resource property 'ensure' at lib/puppet/type/zabbix_host.rb:4.
[warn]: Missing a description for Puppet resource property 'ensure' at lib/puppet/type/zabbix_proxy.rb:4.
[warn]: Missing a description for Puppet resource property 'ensure' at lib/puppet/type/zabbix_template.rb:4.
[warn]: Missing a description for Puppet resource property 'ensure' at lib/puppet/type/zabbix_hostgroup.rb:6.
[warn]: Missing a description for Puppet resource property 'ensure' at lib/puppet/type/zabbix_application.rb:15.
[warn]: Missing a description for Puppet provider 'ruby' (resource type 'zabbix_host') at lib/puppet/provider/zabbix_host/ruby.rb:4.
[warn]: Missing a description for Puppet resource property 'ensure' at lib/puppet/type/zabbix_template_host.rb:14.
[warn]: Missing a description for Puppet provider 'ruby' (resource type 'zabbix_proxy') at lib/puppet/provider/zabbix_proxy/ruby.rb:4.
[warn]: Missing a description for Puppet resource property 'ensure' at lib/puppet/type/zabbix_userparameters.rb:5.
[warn]: Missing a description for Puppet provider 'ruby' (resource type 'zabbix_template') at lib/puppet/provider/zabbix_template/ruby.rb:4.
[warn]: Missing a description for Puppet provider 'ruby' (resource type 'zabbix_hostgroup') at lib/puppet/provider/zabbix_hostgroup/ruby.rb:4.
[warn]: Missing a description for Puppet provider 'ruby' (resource type 'zabbix_application') at lib/puppet/provider/zabbix_application/ruby.rb:4.
[warn]: Missing a description for Puppet provider 'ruby' (resource type 'zabbix_template_host') at lib/puppet/provider/zabbix_template_host/ruby.rb:4.
[warn]: Missing a description for Puppet provider 'ruby' (resource type 'zabbix_userparameters') at lib/puppet/provider/zabbix_userparameters/ruby.rb:4.
In this PR I try to continue the work of fe80 (and others) in PR824.
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.
Fixes #692
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 is a copy of #828, where @bdeferme do not have any more time to work on it. Here I tried to fix the tests.
Fixes #440
This PR adds support for the 2 FPM configurations mentioned here that appear to resolve issues with FPM memory usage on RHEL/CentOS hosts.
No issues related to this PR
Introduce module Hiera data with pre-defined merge behaviour for zabbix::userparameter::data.
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.
<!--
Thank you for contributing to this project!
-->
This PR adds support for the StartODBCPollers
configuration parameter, that was introduced in Zabbix 6.0.
This parameter was already discussed in https://github.com/voxpupuli/puppet-zabbix/issues/814#issuecomment-1042347988, but a PR was never submitted, AFAICT.
<!--
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
-->
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
Import the zabbix timescaledb schema with a boolean flag.
n/a
Adds sensitive support for passwords
Fixes #440
Adds a Puppet provider using the API for the following resources:
- Zabbix Authconfig
- Zabbix User
- Zabbix Usergroup
- Zabbix Roles
n/a
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!
-->
Increases max version of Puppetlabs firewall module to < 6.0.0.
5.0.0 was released which adds support for Puppet 8 and drops support for Puppet 6 which this module already does not support.
N/A
On RHEL systems do not try to install the centos-release-scl package as its not present and fails it
I chose to specifically chose to exclude Red Hat rather than to only trigger when CentOS is detected, i am unclear if the scl release will install on other variants like Rocky or AlmaLinux or not - and figured it was safer to only deal with the specific use case - otherwise this could be changed if required
Fixes #823
<!--
Thank you for contributing to this project!
-->
<!--
When keeping the template options in sync, one option, the template linkage, was missing and could prevent the puppet run from being idempotent.
-->
<!--
None, just an improvement of my previous added option to keep templates in sync.
-->
<!--
Thank you for contributing to this project!
-->
<!--
The PID name seems to have changed in Zabbix6 (hardcoded in zabbix-java-gateway application).
This piece of code fixes it. It was tested on Zabbix 5 and 6.
-->
<!--
None. I was suprised no one had filed an issue about this yet.
-->