Closed swalkinshaw closed 2 years ago
The Ansible ecosystem has changed how their versions and packages work causing the main ansible package versions to no longer determine the version of ansible-playbook. Instead, the new ansible-base package is what matters.
ansible
ansible-playbook
ansible-base
Background: https://blog.while-true-do.io/ansible-release-3-0-0/
For example, installing ansible==2.10.7 would result in ansible-playbook==2.10.16 which was confusing.
ansible==2.10.7
ansible-playbook==2.10.16
By adding ansible-base to our requirements.txt, we'll get more consistent and predictable version constraints.
requirements.txt
Installing ansible-base==2.10.16 would result in ansible-playbook==2.10.16 as you'd expect.
ansible-base==2.10.16
The Ansible ecosystem has changed how their versions and packages work causing the main
ansiblepackage versions to no longer determine the version ofansible-playbook. Instead, the newansible-basepackage is what matters.Background: https://blog.while-true-do.io/ansible-release-3-0-0/
For example, installing
ansible==2.10.7would result inansible-playbook==2.10.16which was confusing.By adding
ansible-baseto ourrequirements.txt, we'll get more consistent and predictable version constraints.Installing
ansible-base==2.10.16would result inansible-playbook==2.10.16as you'd expect.