Starting with ansible version 2.10, ansible and all its modules are no longer provided in a single repository, but split into
ansible-basepackage, which includes some base modules and a collection manager (
- collections, which are installed with
~/.ansible, by default).
See https://github.com/ansible-collections/overview/blob/b7a2e4a3d0ccfb7a9bad9c9c2b41a8337aa2ee16/README.rst#previously-ansible-29-and-earlier for more information on that. With nixos 20.09, nixpkgs provides ansible 2.10 as the default ansible version, which now no longer includes modules that were part of ansible 2.9 and earlier.
Originally, it was enough to enter a nix-shell providing
ansible to be able to run ansible playbooks. Now you need to
- manually install the collections your ansible playbooks depend on, or
- get the necessary collections as nix packages, and research how to point ansible-specific environment variables to the correct locations in the nix-store.
2 is obviously the way you’d like it to work with nix, but nixpkgs currently provides no framework for dealing with collections, so 1 is the current way to do it if you need to get work done. What kind of user interface would nixpkgs even need to have for this to be actually usable and consistent with how other non-reproducible package managers are lifted into nixpkgs? I imagine this could be similar to how python packages are handled, but I don’t know how much effort it is to maintain such a package set.
Any input on how to approach lifting such a package manager into nixpkgs?