# Role var/param naming (prefix)

**URL:** <https://forum.ansible.com/t/role-var-param-naming-prefix/1855>\
**Category:** Get Help\
**Tags:** collections, galaxy-ng\
**Created:** [October 22, 2023, 12:19am UTC](https://forum.ansible.com/t/role-var-param-naming-prefix/1855 "2023-10-22T00:19:16Z")\
**Posts on this page:** 1\
**Showing post:** 3

<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 7, 2024, 7:56am UTC](https://forum.ansible.com/t/role-var-param-naming-prefix/1855/3 "2024-04-07T07:56:48Z")

</div>

I think @evgeni also mentioned something like that not too long ago, IIRC on Matrix, for the Foreman collection. There the role names are short and somewhat generic ([foreman-ansible-modules/roles at develop · theforeman/foreman-ansible-modules · GitHub](https://github.com/theforeman/foreman-ansible-modules/tree/develop/roles)) and you don’t want just these as a prefix. In case of the Foreman collection, all var names start with `foreman_` (or `__foreman_` for private vars), so a first solution (instead of using `# noqa`) was to set `var_naming_pattern`: [foreman-ansible-modules/.ansible-lint at develop · theforeman/foreman-ansible-modules · GitHub](https://github.com/theforeman/foreman-ansible-modules/blob/develop/.ansible-lint#L4)

---

_[View the full topic](https://forum.ansible.com/t/role-var-param-naming-prefix/1855)._