[Announcement] Archival of junipernetworks.junos Collection & Migration to juniper.device

News & Announcements
,
1

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 collection and the official transition to the new consolidated collection:
juniper.device
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?

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

The replacement is:

juniper.device

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

1 Like