# \[Announcement\] Archival of junipernetworks.junos Collection & Migration to juniper.device **URL:** \ **Category:** News & Announcements\ **Tags:** juniper, aap, galaxy-ng\ **Created:** [November 20, 2025, 10:36am UTC](https://forum.ansible.com/t/announcement-archival-of-junipernetworks-junos-collection-migration-to-juniper-device/44869 "2025-11-20T10:36:57Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![rohitthakur2590](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/rohitthakur2590/32/1922_2.png) [@rohitthakur2590](https://forum.ansible.com/u/rohitthakur2590)\ **Post date:** [November 20, 2025, 10:36am UTC](https://forum.ansible.com/t/announcement-archival-of-junipernetworks-junos-collection-migration-to-juniper-device/44869/1 "2025-11-20T10:36:57Z")
Hello Ansible Community, As part of the joint effort between Juniper Networks and the Red Hat Ansible Networking team, we are announcing the archival of the [junipernetworks.junos](https://github.com/ansible-collections/junipernetworks.junos) collection and the official transition to the new consolidated collection: [juniper.device](https://github.com/Juniper/ansible-junos-stdlib) This decision follows the ongoing consolidation work to unify Junos modules, simplify maintenance, and ensure long-term compatibility with the Ansible Automation Platform (AAP). # Why is junipernetworks.junos being archived? The goals of this consolidation are: ### 1. Reduce duplication and fragmentation Historically, Junos support existed in multiple overlapping collections (junipernetworks.junos, ansible-junos-stdlib). The consolidated juniper.device collection provides a single authoritative home for all Junos automation modules. ### 2. Improve CI quality and certification juniper.device is fully aligned with: - the latest ansible-core versions - Ansible content testing standards - Red Hat certification workflows - updated module/linter/sanity requirements This ensures customers receive a reliable and consistently checked collection. ### 3. Support future enhancements All future work—including bug fixes, new features, PyEZ integration improvements, and AAP compatibility—will be done exclusively in the juniper.device collection. # What happens to old releases of [junipernetworks.junos](https://github.com/ansible-collections/junipernetworks.junos)? Nothing breaks. - All previously published versions remain available on Ansible Galaxy and Automation Hub. - Existing playbooks will continue to run without any change. - Only new fixes and features will be provided in juniper.device. The archived collection becomes read-only, meaning: - No new PRs or issues are accepted - No new versions will be published - No certification updates - No downstream support patches # Migration Path For users currently using: [junipernetworks.junos](https://github.com/ansible-collections/junipernetworks.junos) The replacement is: [juniper.device](https://github.com/Juniper/ansible-junos-stdlib) Module names, return structures, and behavior remain consistent. Where necessary, the collection includes compatibility shims and documentation to ensure a smooth transition. # Timeline - juniper.device certified build is currently being prepared for Automation Hub. - Once it is published and validated, junipernetworks.junos will be officially archived. - A final reminder will be sent via The Bullhorn. # Resources - GitHub repository: [GitHub - Juniper/ansible-junos-stdlib: Junos modules for Ansible · GitHub](https://github.com/Juniper/ansible-junos-stdlib) ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [November 21, 2025, 7:29pm UTC](https://forum.ansible.com/t/announcement-archival-of-junipernetworks-junos-collection-migration-to-juniper-device/44869/2 "2025-11-21T19:29:48Z")
[@SteeringCommittee](https://forum.ansible.com/groups/steeringcommittee) [@release-managers](https://forum.ansible.com/groups/release-managers) I think this collection is part of the Ansible Community Package, so we should consider what we should do about this. It’s not deprecated officially yet, but sooner or later I think we should remove it once it is. [Unmaintained collections](https://docs.ansible.com/projects/ansible/devel/community/collection_contributors/collection_package_removal.html#unmaintained-collections) sounds like Ansible… 14? BTW @rohitthakur2590 Thanks for announcing this! So many collections just die silently without anyone telling people ☹ ---
**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:** [November 21, 2025, 8:07pm UTC](https://forum.ansible.com/t/announcement-archival-of-junipernetworks-junos-collection-migration-to-juniper-device/44869/3 "2025-11-21T20:07:56Z")
Yep, we should remove it from Ansible 14 then. It’s a few weeks too late for 13 🙂 ---
**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:** [November 29, 2025, 2:30pm UTC](https://forum.ansible.com/t/announcement-archival-of-junipernetworks-junos-collection-migration-to-juniper-device/44869/4 "2025-11-29T14:30:36Z")
I created a PR to remove it from Ansible 14 (and announce it in the next Ansible 11/12/13 releases): [Remove deprecated junipernetworks.junos from Ansible 14 by felixfontein · Pull Request #631 · ansible-community/ansible-build-data · GitHub](https://github.com/ansible-community/ansible-build-data/pull/631)