ansible: add jmespath by default

[stasjok]

Description of changes

jmespath is needed for a popular jinja filter json_query. It was included by default in ansible_2_9.

We can make it optional, but I think many would like to see it available by default.

Also community.general has filters hashids and jc which also require additional dependencies. Should we include them too?

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 22.05 Release Notes (or backporting 21.11 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
  • (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes
• Fits CONTRIBUTING.md.

[mweinelt]

To be honest, I'm not quite sure what to do about the ansible package. It should probably offer an extraPackages option, to which python packages can be passed, because we simply can't track all dependencies here and different users will need different things and just one broken dependency will break things for all users.

In my real world daily usage we just install ansible-core and handle the rest via collections in requirements.yml, with additional python dependencies being shipped via a requirements.txt.

[stasjok]

I noticed a failed build of deepdiff. It looks like seperman/deepdiff#255. Can I add a package update here or I shouldn't do it? I don't quite sure why ansible-core even depends on it.

It should probably offer an extraPackages option, to which python packages can be passed, because we simply can't track all dependencies here and different users will need different things and just one broken dependency will break things for all users.

I've added extraPackages, but to ansible-core package. This way user can

ansible.override { extraPackages = [ python3Packages.jc ]; }

In my real world daily usage we just install ansible-core and handle the rest via collections in requirements.yml, with additional python dependencies being shipped via a requirements.txt.

I don't see a way to install ansible-core right now with current nixpkgs. python3Packages.ansible package installs only collections (not usable by itself), python3Packages.ansible-core (or just ansible) installs a core with collections. In theory it should be just like upstream: ansible-core installs only core, ansible installs ansible-core which contains "a select group of Collections". In spirit of Nix it would be cool to have something like ansible-core.withPlugins, where a user can provide a list of collections to install (probably just a list of sources fetchFromGithub or even some fetchAnsibleGalaxy fetcher).

[vcunat]

deepdiff was updated as a part of #173429

[stasjok]

deepdiff was updated as a part of #173429

Thanks. I removed it from here. But it looks for me that update is broken (hash is not changed).

[vcunat]

extraPackages: by the way, I recently tried a very simple expression for zabbix-api. I could make a PR but overall I'm unsure how to use the stuff. For now I just

mkShell {
  packages = [ ansible zabbix-api ];
}

[dawidd6]

Would be great to have this.

[mkg20001]

Rebased because of conflict
@mweinelt should we keep the jmespath addition or just go with the extraPackages option? Since the extraPackages option is already useful on it's own.