On Thu, Feb 24, 2022 at 4:54 AM Dick Visser <[email protected]> wrote: > > Right. > > Combining all this information, I do see some sort of bootstrapping problem - > at least in our workflow. > Namely where to start with selecting what version of which package to use. > > Currently we start with ansible==3.4.0. This is because of some issues with > mitogen but that's not really relevant here. > This is part of our requirements.txt which also contains the other packages > that we need. Currently the file looks like: > > ansible==3.4.0
Whoah. There have been quite a few changes in the anible package and its related ansible-core requirement since then. If you're having issues with one of the ansible collection modules, why not just stop installing the ansible bundle? Install only the modules you need, and select the specific version of components you may need. I'm going to restrain my commentary on all the difficulties this confusing split and renaming has generated, and simply say "don't install the ansible package". Select and install only the necessary ansible collection modules as needed for a much more stable, testable, and maintainable server configuration. The current list of nearly 100 third party modules is much, much larger than almost anyone needs and introduces a great deal of testing difficulty. -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAOCN9rz70o-SMDmPRHkhEPi6QyGMgf%2B8OrYo3mhGRLfY9Tg17w%40mail.gmail.com.
