Some folks have forked the repo and are releasing a new role with changes out there. In that context I suggested creating a collection and that seemed to be well received, so the idea is to consolidate the development of OpenWRT code in this collection.
As many routers do not have Python installed nor they have enough space to install it (that’s my case), the role includes some “standard” modules reimplemented (with limitations) as shell scripts. This will be better managed having its own namespace instead of overwriting the names in ansible.legacy.
Hence, could you please create an openwrt repo in the community namespace?
I have not played with that yet, but it would certainly be an interesting feat to have. If you like the idea and have the time, by all means, jump into it .
@Andersson007 is there documentation for collection maintainers specific to configuring these tests? For this collection, all the usual operating systems used in testing are intrinsically irrelevant. We do have molecule tests that use docker images though. I am not sure how’s the best way to integrate those with Zuul.
I would avoid using Zuul for anything more than strictly necessary. Zuul is needed for publishing the collection (since it’s in the community namespace), but for everything else better use GitHub Actions.
.