community.zabbix VS community.hashi_vault

However, there is a breaking change to https://github.com/ansible-collections/community.zabbix/blob/main/plugins/inventory/zabbix_inventory.py which breaks the ability to import host groups from zabbix. This means you'll have all the hosts into one single group.

Use the "official" zabbix collection, there seems no "force psk renewal' present but you could just insert a pre_task to delete it and run the role: https://github.com/ansible-collections/community.zabbix/blob/main/roles/zabbix_agent/tasks/tlspsk_auto_linux.yml

i'm using community.zabbix for deploying the zabbix_agent2 on Windows Machines.

We are happy to welcome several new maintainers in the community.zabbix collection: pyrodie18, BGmot and lzadjsf. Thank you, folks, for your interest and desire to help! Many thanks to D3DeFi, one of the current collection maintainers, for promoting them!

As for automation, I'm about to start playing with: Ansible Collection: Community Zabbix So that might prove useful for you too.

for community.zabbix: With the release of Zabbix 6.0 LTS we would love to get some help on blocking issues like with the integration of a new scripts module. Thank you for your attention!

A lot has been happening in the community.zabbix collection. They've gained two new maintainers, rockaut and ragingpastry, congratulations to both and thank you for your continued great work. The team has recently released version 1.5.1. If you're interested in Zabbix, join the active discussion in #community-zabbix_community:gitter.im via Matrix.

The ansible collection is very good (no one wants to setup manually agent and extend checks with user-parameters manually): https://github.com/ansible-collections/community.zabbix (works for all components).

Yes, each role has their own Molecule configuration and tests. So with every change you make in your role, Molecule will test this. (Keep note: It needs to be executed from Jenkins/GitLab CI/Github Actions etc). Once everything is valid, you will merge the code to master|main. See: https://github.com/ansible-collections/community.zabbix/tree/main/molecule These are the roles I maintain, everytime when someone is creating a PR to add new code/functionality, molecule is executed. When Molecule exits correctly (exit code of 0), then to me the role is ok (In a nutshell). And when the role is ok, I will accept/merge the PR.

My way of doing private SSL (not necessarily the easiest):

* own CA, to be distributed to all systems via Ansible playbook or Dockerfile directives

* Hashicorp Vault with enabled PKI engine

* Ansible Hashivault module [1]

* Ansible role & playbook to tie it all together

* CI enviroment for automated deployment of SSL certs to target systems

Works flawlessly once set up, including restart/reload of affected services. Might do a writeup on my personal blog at some point.

[1] https://github.com/ansible-collections/community.hashi_vault

community.hashi_vault 5.0.0 has been released. See the collection changelog for details.

community.hashi_vault version 4.2.1 has been released with updated documentation for the vault_kv2_write module. There are no functional changes.

community.hashi_vault version 4.2.0 [changelog] has been released with a new KVv2 write module and a warning/deprecation for duplicated term string option use in the hashi_vault lookup.

The community.hashi_vault collection has released version 4.1.0 with a new vault_list module and lookup from a new contributor! There are also some upcoming deprecation announcements for hvac and ansible-core support.

community.hashi_vault version 4.0.0 has been released, with previously announced breaking changes to some default values, and improvements to module documentation with attributes that describe the use of action groups and check mode support.

community.hashi_vault version 3.2.0 has been released with support for the azure auth method, thanks to new contributor @jchenship. This release also includes retries on HTTP 412 and a bugfix affecting requests>=2.28.0.

community.hashi_vault has released version 3.1.0, announcing a change to a default value that will take place in 4.0.0.

The community.hashi_vault collection is looking for feedback about support for end-of-life Python versions going forward. Join the discussion.

community.hashi_vault version 3.0.0 has been released, dropping support for Ansible 2.9 and ansible-base 2.10, as well as removing some deprecated features.