community.zabbix VS community.postgresql

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.

The community.postgresql collection released a new version: 3.2.0.

We are happy to announce that the community.mysql collection has found a new maintainer: Felix Hamme (betanummeric on GitHub/Matrix)! He's also already a maintainer of the community.postgresql collection and has a great history of contributions in both. Thanks, Felix, and welcome to the crew!:)

The community.postgresql collection has released two new version: 1.7.9 and 2.4.1. They revert the breaking change accidentally introduced in the previous version (which was intended for a later major release).

The community.postgresql collection version 2.3.1 has been released (changelog). Thanks to vonschultz and hunleyd!

The community.postgresql team has released 1.7.6 as a bugfix release.

We are also happy to announce a new maintainer of the community.postgresql collection - Felix Hamme (betanummeric on GitHub)! Our congratulations, Felix, and thank you for your great contribution in many collections and desire to help!

The community.postgresql maintainers need your feedback! A proposal for formalizing the supported PG versions has been filed here and needs your input. If adopted, the collection will issue major releases yearly and each major release will officially support the five major version of PG supported at that time. We think this will ultimately improve the collection and improve the end user's experience but we need your input. We look forward to hearing from everyone!

Recently, we opened https://github.com/ansible-collections/community.postgresql/issues/276 to discuss formalizing the supported PostgreSQL versions in the community.postgresql collection. This is a big change for the collection and we want to ensure the proposal makes sense for the collection's users. If you use the collection, please review the proposal and add your thumbs up/down, comment, etc. Thanks!

The community.postgresql collection has released 1.7.3 and 2.1.4 to fully deprecate Ansible 2.9/2.10. Thanks to our newest contributor jchancojr and everyone else involved!