# Announcement: community.openwrt

**URL:** <https://forum.ansible.com/t/announcement-community-openwrt/44964>\
**Category:** Ecosystem Releases\
**Tags:** awx, openwrt, community-openwrt, galaxy-ng\
**Created:** [December 6, 2025, 1:30am UTC](https://forum.ansible.com/t/announcement-community-openwrt/44964 "2025-12-06T01:30:53Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![russoz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/russoz/32/127_2.png) [@russoz](https://forum.ansible.com/u/russoz)\
**Post date:** [December 6, 2025, 1:30am UTC](https://forum.ansible.com/t/announcement-community-openwrt/44964/1 "2025-12-06T01:30:53Z")

</div>

# Community OpenWrt

It is with great joy that I announce to you the first ever release of the collection, [community.openwrt 0.1.0](https://galaxy.ansible.com/ui/repo/published/community/openwrt/).

To install it, you can run the usual:

```
ansible-galaxy collection install community.openwrt

```

This collection is largely adapted from the Ansible role `gekmihesg.openwrt`, and its main feature is that is not a Python-based collection, but rather based on plain shell-scripts, as many OpenWrt devices do not have enough memory hold a Python install. We want to acknowledge the work performed by Markus Weippert and contributors maintaining that Ansible role for many years.

The collection is far from being production-ready but so far it has been performing just like (or similar enough) to the Ansible role, but we would like to invite the community to take a look, add tests, improve the documentation, to contribute by and large. Those who are used to `gekmihesg.openwrt`, there are adjustments to be made, but there is no documentation yet on how to use it. It is in our radar to produce that.

Until we are ready to release a 1.0.0 version the collection is not considered to be stable yet and is subject to breaking changes, sometimes without notices. Again, we appreciate collaborations, but keep in mind this is not stable _just yet_. Watch this space.

---

<div class="post-metadata">

**Author:** ![russoz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/russoz/32/127_2.png) [@russoz](https://forum.ansible.com/u/russoz)\
**Post date:** [December 14, 2025, 8:08pm UTC](https://forum.ansible.com/t/announcement-community-openwrt/44964/2 "2025-12-14T20:08:53Z")

</div>

Hi everyone,

[community.openwrt](https://galaxy.ansible.com/ui/repo/published/community/openwrt/) 0.2.0 was released last evening ([Middle-Earth timezone](https://www.timeanddate.com/worldclock/new-zealand/auckland)).

One of the major issues with this code is that, being shell-based rather Python, it is trickier to “import” the supporting machinery, needed for example to parse and produce JSON content. The `gekmihesg.openwrt` role was performing dark magic overloading internal methods of Ansible’s action plugin code, whilst version 0.1.0 of this collection was brute-forcibly templating the modules’ code into the `wrapper.sh` file. This release brings a much more elegant solution: the wrapper code became a module in itself, and all the regular modules use a standard action plugin that redirects their execution to the wrapper, passing the target (shell) module as parameter.

Other than that, the modules’ docs have received a good dose of attention, and are starting to look fairly good. Still some room for improvement, of course, but we’re getting there.

Anyone interested in collaborating, by all means take a look at the collection’s repo:

> **[GitHub - ansible-collections/community.openwrt](https://github.com/ansible-collections/community.openwrt)**
>
> Contribute to ansible-collections/community.openwrt development by creating an account on GitHub.

Reviews, issues and PRs are more than welcome!

---

<div class="post-metadata">

**Author:** ![russoz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/russoz/32/127_2.png) [@russoz](https://forum.ansible.com/u/russoz)\
**Post date:** [December 27, 2025, 3:00am UTC](https://forum.ansible.com/t/announcement-community-openwrt/44964/3 "2025-12-27T03:00:55Z")

</div>

[community.openwrt](https://galaxy.ansible.com/ui/repo/published/community/openwrt/) 0.3.0 has just been released!

This version adds more documentation and .devcontainer setup, amongst other things. Check the [Changelog](https://github.com/ansible-collections/community.openwrt/blob/main/CHANGELOG.md#v0-3-0) for more details.

---

<div class="post-metadata">

**Author:** ![russoz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/russoz/32/127_2.png) [@russoz](https://forum.ansible.com/u/russoz)\
**Post date:** [December 29, 2025, 10:54am UTC](https://forum.ansible.com/t/announcement-community-openwrt/44964/4 "2025-12-29T10:54:56Z")

</div>

Yay! More people are starting to use `community.openwrt`!! 😄

I posted a [message in the OpenWrt Forum](https://forum.openwrt.org/t/ansible-and-openwrt/223234/5) and some days later we already have people making their own projects using community.openwrt! I very excited with this!! The New Year is going to bring more good news and fantastic automations for us 🙂

🥳 🍩 🚀

---

<div class="post-metadata">

**Author:** ![russoz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/russoz/32/127_2.png) [@russoz](https://forum.ansible.com/u/russoz)\
**Post date:** [January 6, 2026, 12:11am UTC](https://forum.ansible.com/t/announcement-community-openwrt/44964/5 "2026-01-06T00:11:01Z")

</div>

[community.openwrt](https://galaxy.ansible.com/ui/repo/published/community/openwrt/) 0.4.0 has just been released!

This version comes with integration tests (currently only for one module, we will soon expand to others), improved lifecycle functions for the shell-based modules, and a brand new module `community.openwrt.apk`, supporting the upcoming release of OpenWrt 25.12.

Check the [Changelog](https://github.com/ansible-collections/community.openwrt/blob/main/CHANGELOG.md) for more details.

---

<div class="post-metadata">

**Author:** ![russoz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/russoz/32/127_2.png) [@russoz](https://forum.ansible.com/u/russoz)\
**Post date:** [January 6, 2026, 12:33am UTC](https://forum.ansible.com/t/announcement-community-openwrt/44964/6 "2026-01-06T00:33:18Z")

</div>

For the record, there was a snafu in the release of 0.3.0 - yours truly did not wait for the Zuul publishing to complete, and there was an error: galaxy-importer flagged missing README files in the collection’s roles, so that version was NOT published to Ansible Galaxy.

Please use the newly released version 0.4.0 instead.

---

<div class="post-metadata">

**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\
**Post date:** [January 6, 2026, 7:21am UTC](https://forum.ansible.com/t/announcement-community-openwrt/44964/7 "2026-01-06T07:21:07Z")

</div>

> [@russoz](#):
>
> Yay! More people are starting to use `community.openwrt`!! 😄
> 
> I posted a [message in the OpenWrt Forum](https://forum.openwrt.org/t/ansible-and-openwrt/223234/5) and some days later we already have people making their own projects using community.openwrt!

That’s amazing.

---

<div class="post-metadata">

**Author:** ![russoz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/russoz/32/127_2.png) [@russoz](https://forum.ansible.com/u/russoz)\
**Post date:** [February 15, 2026, 9:17pm UTC](https://forum.ansible.com/t/announcement-community-openwrt/44964/8 "2026-02-15T21:17:14Z")

</div>


