# Module Defaults + ansible-lint

**URL:** <https://forum.ansible.com/t/module-defaults-ansible-lint/42703>\
**Category:** Get Help\
**Tags:** ansible-lint\
**Created:** [May 16, 2025, 5:42pm UTC](https://forum.ansible.com/t/module-defaults-ansible-lint/42703 "2025-05-16T17:42:12Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lyle\_McKarns](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/lyle_mckarns/32/8142_2.png) [@Lyle\_McKarns](https://forum.ansible.com/u/Lyle_McKarns)\
**Post date:** [May 16, 2025, 5:42pm UTC](https://forum.ansible.com/t/module-defaults-ansible-lint/42703/1 "2025-05-16T17:42:12Z")

</div>

Folks - I was wondering if anyone has come up with a working solution to using both the `module_defaults` feature and `ansible-lint`? I’ve been following [this issue](https://github.com/ansible/ansible-lint/issues/2953) for a while now, and seen no progress/updates (other than bumps) in quite a while.

The issue is that if you set `module_defaults` rather than provide (for example) the same connection information to a half dozen tasks in a row, `ansible-lint` will throw errors about missing required arguments (because its not seeing them in the `module_defaults` section). This means, at least as far as I can tell, that you can’t use this feature while also doing linting of even the most basic of files without disabling test.

#ansible-lint