Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crank the Handle: Update Ansible #8

Open
ian-jarrett opened this issue Oct 14, 2021 · 3 comments
Open

Crank the Handle: Update Ansible #8

ian-jarrett opened this issue Oct 14, 2021 · 3 comments
Assignees

Comments

@ian-jarrett
Copy link
Contributor

Ansible 2.11 and 2.12 are stable.

@wildsubnet
Copy link
Contributor

https://www.juniper.net/documentation/us/en/software/junos-ansible/ansible/topics/task/junos-ansible-server-installing.html

"Ansible supports Ansible Content Collections, or collections, starting in Ansible 2.10. With the introduction of the juniper.device collection, the modules in the Juniper.junos role were duplicated under new names in the collection and thus retain the same functionality and parameters as the original modules, with the exception of the provider parameter. Although the Juniper.junos role can coexist with the juniper.device collection and will work in later releases, new features are only being added to the juniper.device collection going forward."

@wildsubnet
Copy link
Contributor

Latest alpine uses Ansible 2.10, which is still the "new train". Works with the old galaxy modules. Will work on updating that next.

@wildsubnet
Copy link
Contributor

Pull request 19 contains updated alpine/ansible files.
I've removed the legacy ansible roles and done a test run on my fork. Would like to test it a little harder when I get chance before creating a pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants