[Vote ended on 2024-10-07] Should we remove community.network from the Ansible community package?

felixfontein
Wed, 21 Aug 2024 19:17:09 +0000
Project Discussions

At today’s community meeting we were talking (again) about tests for all collections included in the Ansible community package, from where the discussion ended up with community.network.

Right now community.network is not actively maintained (there’s basic maintenance done by @Andersson007, but that’s basically it). The last feature release was in 2022, and in the last 12 months there only have been a few bugfixes.

There seem to be some users of that collection, but there don’t seem to be many (or none at all?) active module maintainers anymore. The last batch of reported sanity errors (Community package requirements: sanity tests · Issue #591 · ansible-collections/community.network · GitHub) is basically still there, since nobody wants to work on them.

One thing that might still be used more are redirects in meta/runtime.yml. There are 46 redirects to other collections, but more than half of these go to community.fortios, which we already removed from the Ansible community package, and several more to cisco.nso (which we also removed). Then there are a few redirects to community.routeros, and one to fortinet.fortimanager (for a httpapi plugin). So from the redirects, only community.routeros users might suffer from short names no longer working. (Whether anyone is still using the community.routeros shortnames is another question.)

So, what do you think? Should we keep it? Remove it? Or are you even an active user of something that’s included in community.network? Please tell us

49 posts - 8 participants