Hey ! since ansible-2.10 the modules are migrate to ansible-galaxy collections [1]. So I was searching the missing modules, and missed them a couple of times, so I wanted to share how I ended installed them. The general collection (all default modules) [2], and you can install it by: $ ansible-galaxy collection install community.general Maybe it can usefull to add a post-install message for the users ? Guillaume 1: https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_2.10.html 2: https://galaxy.ansible.com/community/general
Just updated and figured that a large number of my playbooks are broken. Not to speak of general settings like stdout_callback in ansible.cfg. There should be warning at least. I was reading the docs and it seems like there is some community version that should be like Ansible 2.9: https://github.com/ansible-collections/overview/blob/main/README.rst#q-once-the-next-version-of-ansible-is-released-will-my-playbooks-still-work It states: Q: Once the next version of Ansible is released, will my playbooks still work For users of the community version of ansible pip/apt-get install ansible will continue to give you a working install of Ansible including the three thousand plus modules that previously shipped with Ansible 2.9. This sounds as if the PIP / Debian / Ubuntu version will be shipped as it was before 2.10. But maybe i am getting it wrong. Somehow it would be awesome if there would be a way to get some of the most common community modules and plugins as useflags.
Hey, (In reply to r7l from comment #1) > https://github.com/ansible-collections/overview/blob/main/README.rst#q-once- > the-next-version-of-ansible-is-released-will-my-playbooks-still-work > > This sounds as if the PIP / Debian / Ubuntu version will be shipped as it > was before 2.10. But maybe i am getting it wrong. I was thinking the same, it is a surprising move, but installing the collection solve it.
Ok let's close this
