gardar
gardar
That is true but it simply passes the parameters down to the underlying module that it's proxy-ing. https://docs.ansible.com/ansible/latest/collections/ansible/builtin/package_module.html#id1
Ugh, I don't like this. Raised my concerns over at https://github.com/ansible/ansible-lint/issues/4035#issuecomment-2116272270
superseded by https://github.com/prometheus-community/ansible/pull/363
What distro are you on?
Is that the target system or your control host? The `package_facts` module supports pacman so you should get the package facts on Arch
Hmm, debian bookworm should also definitely work. Does the https://github.com/prometheus-community/ansible/blob/196bd2fd96840b3e62527a447e54c9975d33a964/roles/node_exporter/tasks/preflight.yml#L19-L21 task run on that host?
Interesting, I wonder if it's attempting to use the wrong package manager when it's set to `auto` As a workaround, perhaps you could enforce the apt manager with [module_defaults](https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_module_defaults.html) in...
Oh that sounds like a mess, I thought the `auto` was using the package manager from the facts already. Implementing a package manager detection in two places feels unnecessary. 🤔
Looks like this has been fixed in Ansible https://github.com/ansible/ansible/pull/83149
Please fix the DCO