Felix Fontein

Ping @yousefenzhad needs_info

@yousefenzhad another ping :) needs_info

Variables are lazily evaluated. This means that this lookup is called *every single time* `ansible_become_password` is used. Better use `set_fact` as a first task (or pre-task) to obtain the password...

You might want to add `run_once: true` to the `set_fact` task to speed this up even a bit further :)

Ping @zollo needs_info

Thanks for your contribution! If anyone is wondering how to do this with pure ansible-core + jinja: ```yaml - hosts: localhost gather_facts: false tasks: - ansible.builtin.debug: msg: >- {{ input...

@bcoca we already have a filter for removing *keys* from dictionaries: `community.general.remove_keys`. This PR is about removing specific *values* (in particular `None`).

> Let me know if you want to track it with issue. Using this PR for discussions is also fine IMO.

Regarding [my question](https://github.com/ansible-collections/community.general/pull/10139#issuecomment-2884817792) about why not allow arbitrary Jinja2 tests, similar as for the `reject` filter (https://jinja.palletsprojects.com/en/stable/templates/#jinja-filters.reject). > For the key we have the filter and the map, but i...

The `reject` filter (look at its docs!) allows to use arbitrary Jinja2 tests, like `some_list | reject("eq", "foo")` will remove all entries in `some_list` that are equal to the string...