# Would maintainers be open to have facts set for the auth arguments for tasks?

**URL:** <https://forum.ansible.com/t/would-maintainers-be-open-to-have-facts-set-for-the-auth-arguments-for-tasks/45713>\
**Category:** Get Help\
**Tags:** proxmox\
**Created:** [April 21, 2026, 3:23am UTC](https://forum.ansible.com/t/would-maintainers-be-open-to-have-facts-set-for-the-auth-arguments-for-tasks/45713 "2026-04-21T03:23:44Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![roleroz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/roleroz/32/7762_2.png) [@roleroz](https://forum.ansible.com/u/roleroz)\
**Post date:** [April 21, 2026, 3:23am UTC](https://forum.ansible.com/t/would-maintainers-be-open-to-have-facts-set-for-the-auth-arguments-for-tasks/45713/1 "2026-04-21T03:23:44Z")

</div>

When connecting to hosts through SSH you can set the auth parameters with connection arguments, or ansible can use the generic ones (like ansible\_ssh\_pass), but every time I use a task from community.proxmox I need to set a handful of values for things that normally don’t change during a playbook (api\_host, api\_user, api\_password and node). Would the maintainers be open to having facts set that would be used in case those arguments were not provided? That would make the tasks more readable by removing boilerplate

I haven’t seen how to do it, but I’m happy to write that code myself and send it out. At this point I’m trying to check if people would be ok with that before spending the time doing it 😉

---

<div class="post-metadata">

**Author:** ![kks](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/kks/32/10352_2.png) [@kks](https://forum.ansible.com/u/kks)\
**Post date:** [April 21, 2026, 6:21am UTC](https://forum.ansible.com/t/would-maintainers-be-open-to-have-facts-set-for-the-auth-arguments-for-tasks/45713/2 "2026-04-21T06:21:31Z")

</div>

There is already functionality in ansible for that - module defaults

> **[module\_defaults - Module defaults — Ansible Community Documentation](https://docs.ansible.com/projects/ansible/latest/playbook_guide/playbooks_module_defaults.html#module-defaults)**
>
> If you frequently call the same module with the same arguments, it can be useful to define default arguments for that particular module using the module\_defaults keyword.

And module defaults groups

> **[meta/runtime.yml - Module defaults — Ansible Community Documentation](https://docs.ansible.com/projects/ansible/latest/playbook_guide/playbooks_module_defaults.html#module-defaults-groups)**
>
> If you frequently call the same module with the same arguments, it can be useful to define default arguments for that particular module using the module\_defaults keyword.

---

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [April 21, 2026, 3:57pm UTC](https://forum.ansible.com/t/would-maintainers-be-open-to-have-facts-set-for-the-auth-arguments-for-tasks/45713/3 "2026-04-21T15:57:40Z")

</div>

Note that community.proxmox provides a module defaults group `group/community.proxmox.proxmox`, documented for example here: [community.proxmox.proxmox module – Management of instances in Proxmox VE cluster — Ansible Community Documentation](https://docs.ansible.com/projects/ansible/latest/collections/community/proxmox/proxmox_module.html#attribute-action_group)

---

<div class="post-metadata">

**Author:** ![roleroz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/roleroz/32/7762_2.png) [@roleroz](https://forum.ansible.com/u/roleroz)\
**Post date:** [April 22, 2026, 5:04pm UTC](https://forum.ansible.com/t/would-maintainers-be-open-to-have-facts-set-for-the-auth-arguments-for-tasks/45713/4 "2026-04-22T17:04:42Z")

</div>

Awesome, thanks for the pointers, I’ll look into this