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.
@russoz I’ve added the repo to Zuul configs to have the collection published by Zuul when it sees tags (as usual). Also added our standard branch protection rules.
You’re admin, GitHub - ansible-collections/community.openwrt enjoy and thanks!
Please reach out to me directly if you need any assistance
I wish I had more time. I have a pretty cool (sh+uci-defaults+imagebuilder) automation for immutable deployments locally, with the possibility to flash the exact same image onto multiple nodes and have them self-configure on boot. The reason it’s not published is because there’s secrets being injected (not just in text files but also mac addresses in directory names) and I haven’t had a chance to separate them from shareable bits (plus there’s a lot of disorganized mess in-between). Maybe, one day.
(I have left this message in the openwrt role repo, this is just to address the forum readers as well)
Sorry for the long radio silence. I managed to make progress with the collection. There is an initial PR in place right now:
that’s mostly for boilerplate and metadata updates, but after that one comes through, I have this git branch waiting to go:
It has a (limited) test suite using molecule - testing against multiple versions of OpenWRT and the CI workflows have not been really tested yet. However, I have this (private) repo with my OpenWRT playbook to configure my home router, and that branch’s code is working in there.
That being said, I think it is time to stop using this issue/repo forum post and start discussing things in the collection’s repo: GitHub - ansible-collections/community.openwrt (or in new posts, for specific topics).
I am starting to raise issues in the git repo to give visibility of the things we need to work on. Hope to see you guys over there!
.