Dusan Matejka

I agree with this. Support matrix should be way smaller then it is. No need to support EOL releases

I would like to work with f strings and wallruses :( But I believe that we need to follow ansible in this since we will be included in the releases

Theoretical: what would happen if drop py2.x after 1.0.0, start working only on 2.0.0 and only backport small changes? How would this look with 1.x.0 releases? This would probably lock...

I may have miss-lead you with a check mode :disappointed: https://docs.ansible.com/ansible/latest/dev_guide/developing_modules_general.html#creating-an-info-or-a-facts-module it seems they must to support check mode? Probably a reason why this fails. I am so sorry

thank you for the suggestion @amartin3225 . The requests seems reasonable and doable, although I am not sure when we would be able to address it. If you are considering...

@marcusjfloyd is this something that is still happening to you? Have you perhaps had a chance to upgrade to ansible >= 2.10 to see if the issue persists?

Oh my, they have switched from using IDs to UUIDs! See #451

Honestly I have no idea. But CI for zabbix_template is no longer failing and we are preparing to drop 5.4 as well, so lets ignore this and whoever finds this...

I think this would first need custom module plugin. It is kind of unwritten rule that everything manageable via API should eventually have its own module. Zabbix roles are usually...

Indeed, good tip :) Thanks!