community.zabbix VS azure

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.

There is already a successor collection, azure.azcollection, in the community package which should cover the same functionality.

Looks like there is a work in progress PR to fix this in https://github.com/ansible-collections/azure/pull/1112

https://github.com/Azure/WALinuxAgent - I think this is the equivalence of GCP guest-agent, serving similar functionalities, and is pre-installed on all official images, otherwise basic things like authentication and image baking will break.

By setting the provisionVMAgent property to false when creating a virtual machine, WALinuxAgent should run with all extensions disabled, and I think that's as minimal as a Linux VM can go on Azure.

This property, however, can't be set via https://github.com/ansible-collections/azure, which is of course another lovely OSS project by Microsoft. I didn't bother to send a PR.

The OMI agent seems to be a different beast that is way more obnoxious. The closest thing on GCP is probably the collectd agent and the fluentd agent installed for Stackdriver Monitoring and Stackdriver Logging? Plus whatever OS config to enable unattended upgrades.

I just learnt from this HN thread about the SSM agent on AWS. That one does seem equally obnoxious as the OMI agent.

https://github.com/ansible-collections/azure or https://docs.ansible.com/ansible/latest/collections/azure/azcollection/index.html#plugins-in-azure-azcollection or https://galaxy.ansible.com/azure/azcollection are all for the same project that manages the azure ansible modules.

So I created a bug - 445