5 ms·

Regarding Ansible, I still default to installing with `pip3 install ansible`, which installs the "Ansible Community Distribution" (which is still called "Ansibl

Regarding Ansible, I still default to installing with `pip3 install ansible`, which installs the "Ansible Community Distribution" (which is still called "Ansible" even though it seems "ansible-core" is also called "Ansible", but there's also "Ansible by Red Hat" which is the 'Ansible Automation Platform' which includes Tower and other related products...). The ACD (or what I still call "Ansible") includes everything that was traditionally part of Ansible, and then some, just bundled up into one big install instead of requiring you to install ansible-core then pick and choose collections to install on top. This covers about 99.9% of all use cases (for Ansible for automation work) still, and for anything else, you can add your own roles or install an additional community collection or two.

notabee 4y ago
After much struggle, I reached the same conclusion. And it gets around the problem of downloading collections only to find that they don't support the version of python on the system you're trying to use it on. But since those collections get stored in python site-packages instead of anything in ANSIBLE_COLLECTIONS_PATH, it's still kind of confusing. And I still haven't checked what happens if a teammate accidentally installs the latest collection version locally in their home from Galaxy as well (a stupid default imho). I understand why collections got split out due to development needs, but the switch over to them has been pretty crappy from a user perspective.