related / possible first task: https://github.com/ansible/ansible/issues/43385[1] it looks as if it's actually a zypper bug / design decision to always return 0 when run on "full autopilot". should we implement the workaround suggested on github, or file a bug against zypper? Cheers MH Am Mittwoch, 14. August 2019, 12:01:17 CEST schrieb Jean-Philippe Evrard:
Hello everyone,
I will start with sad news: the Ansible zypper* modules [1][2] don't have maintainers anymore.
To fix this, I signed myself up to be a maintainer of those modules, under a newly created team, "Team SUSE". However, I think it would be nice to "spread the work" between multiple people. We don't need to offer anything else than help maintaining those modules, as this is a community effort, and a community "support".
Through this email, I would like to encourage people of the openSUSE community to help me maintain these modules. If you're interested, please contact me, and/or propose a PR to Ansible's botmeta to join the team.
Thank you in advance!
Regards, Jean-Philippe Evrard
[1]: https://docs.ansible.com/ansible/latest/modules/zypper_repository_module.htm l [2]: https://docs.ansible.com/ansible/latest/modules/zypper_module.html
*Mathias Homann* Mathias.Homann@openSUSE.org[2] telegram: https://telegram.me/lemmy98[3] irc: [lemmy] on freenode and ircnet obs: lemmy04 *gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102 * -------- [1] https://github.com/ansible/ansible/issues/43385 [2] mailto:Mathias.Homann@eregion.de [3] https://telegram.me/lemmy98 -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org