# Community.routeros: 3.17.0-a1 pre-release with many new and updated paths is ready for intensive testing!

**URL:** <https://forum.ansible.com/t/community-routeros-3-17-0-a1-pre-release-with-many-new-and-updated-paths-is-ready-for-intensive-testing/45228>\
**Category:** Collection Development\
**Tags:** mikrotik, routeros, testing\
**Created:** [January 30, 2026, 8:24pm UTC](https://forum.ansible.com/t/community-routeros-3-17-0-a1-pre-release-with-many-new-and-updated-paths-is-ready-for-intensive-testing/45228 "2026-01-30T20:24:48Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [January 30, 2026, 8:24pm UTC](https://forum.ansible.com/t/community-routeros-3-17-0-a1-pre-release-with-many-new-and-updated-paths-is-ready-for-intensive-testing/45228/1 "2026-01-30T20:24:48Z")

</div>

We just released [community.routeros 3.17.0-a1](https://github.com/ansible-collections/community.routeros/releases/tag/3.17.0-a1) ([changelog](https://github.com/ansible-collections/community.routeros/blob/main/CHANGELOG.md#v3-17-0-a1)), whose main difference to 3.16.0 is [a Pull Request by Felix Ricke](https://github.com/ansible-collections/community.routeros/pull/433) that adds and updates many paths for the `community.routeros.api_modify` and `community.routeros.api_info` modules. Since this is a very massive update, which is mainly automatically extracted from RouterOS releases, it also means that most changes couldn’t be tested. This is where we need the community’s help!

If you have RouterOS instances and use community.routeros with them (that use the `api_modify` and `api_info` modules), please check out the pre-release and test your roles and playbooks with this version. And make sure to first test them in **check mode** (`ansible-playbook ... --check`)! Also `--diff` will be useful to see what would change.

Please report any problems which you think are bugs caused by this changes in the [community.routeros issue tracker on GitHub](https://github.com/ansible-collections/community.routeros/issues/new/choose). You can of course also use this thread to discuss the changes 🙂

Thanks a lot in advance!

---

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [January 30, 2026, 8:27pm UTC](https://forum.ansible.com/t/community-routeros-3-17-0-a1-pre-release-with-many-new-and-updated-paths-is-ready-for-intensive-testing/45228/2 "2026-01-30T20:27:40Z")

</div>

Pinging @rbur004 and @hirnpfirsich since you asked questions about the collection on the forum.

---

<div class="post-metadata">

**Author:** ![hirnpfirsich](https://avatars.discourse-cdn.com/v4/letter/h/a9adbd/32.png) [@hirnpfirsich](https://forum.ansible.com/u/hirnpfirsich)\
**Post date:** [January 31, 2026, 1:59pm UTC](https://forum.ansible.com/t/community-routeros-3-17-0-a1-pre-release-with-many-new-and-updated-paths-is-ready-for-intensive-testing/45228/3 "2026-01-31T13:59:02Z")

</div>

Thank you @felixfontein !  
I"ll try to validate a few of the new paths 🙂

Any specifics on the time window till release ?

---

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [January 31, 2026, 2:32pm UTC](https://forum.ansible.com/t/community-routeros-3-17-0-a1-pre-release-with-many-new-and-updated-paths-is-ready-for-intensive-testing/45228/4 "2026-01-31T14:32:33Z")

</div>

I was originally thinking of “a bit later” ([Add and update various RouterOS paths and parameter definitions by FelixRicke · Pull Request #433 · ansible-collections/community.routeros · GitHub](https://github.com/ansible-collections/community.routeros/pull/433#issuecomment-3796750283)), like 1-2 weeks, depending on how much and what kind of feedback comes in. I’d like to avoid having a “proper” release directly before the next Ansible release (so either at least one week before it, or somewhen after it) to avoid a potentially broken version ending up in there (for four weeks).

I don’t mind waiting longer though, if that helps for testing (or seems necessary from the feedback).

---

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [February 8, 2026, 3:40pm UTC](https://forum.ansible.com/t/community-routeros-3-17-0-a1-pre-release-with-many-new-and-updated-paths-is-ready-for-intensive-testing/45228/5 "2026-02-08T15:40:43Z")

</div>

There’s now [another pre-release 3.17.0-a2 with a few bugfixes](https://github.com/ansible-collections/community.routeros/blob/main/CHANGELOG.md#v3-17-0-a2).

---

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [February 16, 2026, 9:15pm UTC](https://forum.ansible.com/t/community-routeros-3-17-0-a1-pre-release-with-many-new-and-updated-paths-is-ready-for-intensive-testing/45228/6 "2026-02-16T21:15:34Z")

</div>

There’s now [another pre-release 3.17.0-a3 with more bugfixes](https://github.com/ansible-collections/community.routeros/blob/main/CHANGELOG.md#v3-17-0-a3).

---

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [February 22, 2026, 2:39pm UTC](https://forum.ansible.com/t/community-routeros-3-17-0-a1-pre-release-with-many-new-and-updated-paths-is-ready-for-intensive-testing/45228/7 "2026-02-22T14:39:08Z")

</div>

If there are no new reactions, I plan to do a release of 3.17.0 in the next few days (after the Ansible 13.4.0 release).

---

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [March 5, 2026, 9:31pm UTC](https://forum.ansible.com/t/community-routeros-3-17-0-a1-pre-release-with-many-new-and-updated-paths-is-ready-for-intensive-testing/45228/8 "2026-03-05T21:31:19Z")

</div>

[3.17.0 is now out](https://github.com/ansible-collections/community.routeros/blob/main/CHANGELOG.md#v3-17-0)!
