# What should we call infra.\*\_configuration?

**URL:** <https://forum.ansible.com/t/what-should-we-call-infra-configuration/39163>\
**Category:** Project Discussions\
**Tags:** infra-config-as-code\
**Created:** [December 15, 2024, 1:12pm UTC](https://forum.ansible.com/t/what-should-we-call-infra-configuration/39163 "2024-12-15T13:12:31Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![akira6592](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/akira6592/32/222_2.png) [@akira6592](https://forum.ansible.com/u/akira6592)\
**Post date:** [December 15, 2024, 1:12pm UTC](https://forum.ansible.com/t/what-should-we-call-infra-configuration/39163/1 "2024-12-15T13:12:31Z")

</div>

For example, `infra.controller_configuration` collection calls modules of `ansible.controller` collection.

Summary:

| Group “A” Collections | Group “B” Collections |
| --- | --- |
| infra.aap\_configuration | ansible.platform, ansible.controller, ansible.ah, ansible.eda |
| infra.controller\_configuration | ansible.controller |
| infra.ah\_configuration | ansible.ah |
| infra.eda\_configuration | ansible.eda |

What should we call above Group “A” and “B” collections?