On Fri, 25 Feb 2022 at 00:29, Nico Kadel-Garcia <[email protected]> wrote:
> 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? As said earlier, we use 3.4.0 because that works with mitogen. We don't have problems with collections. Install only the modules you need, and > select the specific version of components you may need. > > Yes, I know that, and this is what I pointed out. The final question remains unanswered though: what versions of modules go with a specific ansible-base/core version? If there is no such mapping, then I'll have to manually go through the collections and decide what's best. After all, it is now only about 8 collections (in our case), instead of ~100. Still interested in a better solution if that exists. -- Dick Visser Trust & Identity Service Operations Manager GÉANT -- 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/CAL8fbwM11O2GFE1UWPV3OmykJkgZz4kFqm-80z61Hy7%3DSL3zEA%40mail.gmail.com.
