Dusan Matejka

@opulasli414 did you try with fixed version? E.g. either: ``` rights: - host_group: "{{ item.host_group }}" permission: read-only ``` or: ``` rights: - host_group: "{{ item.host_group }}" permission: read-write ```...

> Something around the lines of: > > user_groups: > > * name: Admins > > * host_group: > - name: MyTestingHostGroup101 > permission: read-write > - name: MyTestingHostGroup102 >...

Oh, I finally understand! :) Well, this is something that we are not supporting in the modules unfortunately. We mimic the way it is done via official Zabbix API: https://www.zabbix.com/documentation/current/en/manual/api/reference/usergroup/create...

Included latest merges to the repository & re-run antsibull-changelog. This is now ready for review && merge

As a workaround, try to set them in the https://github.com/ansible-collections/community.zabbix/blob/main/tests/integration/targets/setup_zabbix/defaults/main.yml This test roles is included from every other role. I am not sure if this is a good permanent place...

I would guess it doesn't build anything and rather defaults to localhost as usually. `ansible-test` can be locked inside of a container or run on a host (which we are...

> 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....

> > 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...

> 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...

> > 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....