Evgeny

To be honest I'd rename this module to either zabbix_api_info or zabbix_api_facts.

I am not sure. Zabbix 4.0 still has limited support until October 31, 2023 https://www.zabbix.com/life_cycle_and_release_policy Why remove what's working? Or you mean to put some 'deprecation notice'?

We have this test https://github.com/ansible-collections/community.zabbix/blob/main/tests/integration/targets/test_zabbix_usergroup/tasks/main.yml#L70 Never fails. Moreover in your code you are trying to give read-only and read-write permissions to the same host_group. ``` rights: - host_group: "{{ item.host_group...

This is what works in this repo tests: ``` - name: test - update Zabbix user group with multiple rights zabbix_usergroup: rights: - host_group: Discovered hosts permission: read-only - host_group:...

I currently can't successfully run mentioned in https://github.com/ansible-collections/community.zabbix/pull/444 code. Silly question how do I provide these variables if I run `ansbile-test integration`? ``` --- # hosts.yml all: children: api: hosts:...

Yes, thanks, already tried that and it worked. I am just curious (and did not find anything meaningful on the Internet) how ansible-test "builds" the inventory and against what host...

Spent some time learning how connection plugins work and I mus say it's very cool stuff. I have a question about introducing `connection_type` variable as proposed above. Why don't we...

Yes of course I am working off your implementation. I am setting `_zapi` property to an instance of `ZabbixApiRequest` instead of `ZabbixAPI`. Some modules just work with this with no...

> Maybe we can word it that zabbix-api is still possible opt-in, but will not be supported and is unmaintained by us. In such case we can also leave a...

I need an advise on what we should do with documentation and hard requirements for these all modules parameters `server_url`, `login_user`, `login_password`, they are not needed for httpapi. I propose...