Updating to latest instead of 4.4.5
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
-->
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
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 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!
-->
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
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)
<!--
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!
-->
<!--
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!
-->
<!--
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
-->
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.
Add acceptance test for proxy installation
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
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