community.zabbix VS ansible.netcommon

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.

ansible.netcommon has been released with bugfixes (changelog).

ansible.netcommon 5.0.0

Would you share the version of netcommon/ ansible-core version installed for you? and please file an issue here, https://github.com/ansible-collections/ansible.netcommon/issues. Regards

There have been a few networking releases this week: * ansible.netcommon 3.1.0 has been released with new features (changelog) * cisco.ios 3.3.0 has been released with new features (changelog) * cisco.iosxr 3.3.0 has been released with new features (changelog)

The ipaddr filters are broken in ansible.netcommon 2.6.0 release as we have recently migrated ipaddr filters from ansible.netcommon to ansible.utils. We have released utils 2.5.2 and netcommon 2.6.1 which fixed these two issues (ansible.netcommon#375, ansible.utils#148). For the FQDN issue, the ansible-core team has already merged the fix. This fix will be available in the March 28th release, which means that users of non fqdn ipaddr filters can use the old netcommon collection version 2.5.1 as a workaround until the next ansible-core release (March 28th) by the core-team. For fqdn ipaddr filters, users can use the latest versions of any of ansible.netcommon (2.6.1) or ansible.utils (2.5.2).

This also affected net_get. New pull request to address this: https://github.com/ansible-collections/ansible.netcommon/pull/199