community.zabbix VS community.general

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.

community.general 7.0.0 has been released with some new modules, a lot of new features, and a lot of bugfixes. Please make sure to look at least at the sections Breaking Changes and Removed Features in the changelog to figure out whether you need to change something in your roles or playbooks.

community.general 6.5.0 (changelog) has been released with new features, bugfixes, and new plugins. Note that the next minor 6.x.y release will be 6.6.0 on April 24th, and after that the next minor/major release will be 7.0.0 on May 8th. That is one week before May 15th, the feature freeze date for Ansible 8.

community.general 6.2.0 (changelog) has been released. Please note that the Rackspace modules might get deprecated in version 7.0.0 and removed in version 9.0.0, since the Python library they are based on (pyrax) has been deprecated for a long time. If you are interested in maintaining and improving (potentially partially rewriting?) the modules to avoid removal, please look at the GitHub issue discussing this.

community.general 6.0.0 (changelog) has been released! Besides a lot of new features and bugfixes, new modules and plugins, some deprecations and breaking changes, a major change to 5.x.y is that the plugins/modules/ directory tree structure has been removed. Please check out the changelog for more details!

The module docs can be found here. The source can be found here.

We are looking at reducing the maintenance for old stable branches for community.general and community.network collection repositories. We'd welcome your feedback, in particular if you think you may be negatively impacted by the change. Full details of the proposal, and the ability to record your vote can be done via community-topic#55.

community.general 3.8.3 has been released with some bugfixes (changelog).

If you are missing metrics or something else from the logstash callback it could be an opportunity to contribute it upstream: https://github.com/ansible-collections/community.general/blob/main/plugins/callback/logstash.py