# Collections namespace collisions

**URL:** <https://forum.ansible.com/t/collections-namespace-collisions/32519>\
**Category:** Ansible Project\
**Created:** [March 24, 2020, 1:58am UTC](https://forum.ansible.com/t/collections-namespace-collisions/32519 "2020-03-24T01:58:32Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Orion\_Poplawski](https://avatars.discourse-cdn.com/v4/letter/o/c2a13f/32.png) [@Orion\_Poplawski](https://forum.ansible.com/u/Orion_Poplawski)\
**Post date:** [March 24, 2020, 1:58am UTC](https://forum.ansible.com/t/collections-namespace-collisions/32519/1 "2020-03-24T01:58:32Z")

</div>

I just discovered that you can use:

collections:

- my\_namespace.my\_collection

in a playbook to avoid having to type the FQCN of a module. However, how are namespace collisions handled? It seems impractical that every collection would have unique module names. In fact I was counting on people’s use of FQCN to allow me to shorten my collections’ module names. So I ended up with a module named ‘pfsensbile.core.setup’ that is conflicting with the built in ‘setup’ module when ‘collections: - pfsensible.core’ is used in the play. See [https://github.com/opoplawski/ansible-pfsense/issues/44](https://github.com/opoplawski/ansible-pfsense/issues/44). Is it possible to avoid this? In some way it seems like ansible itself should always prefer its own core modules.