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. Is it possible to avoid this? In some way it seems like ansible itself should always prefer its own core modules. -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/8cb728a4-ccef-45b9-a1bd-dcc3a148079b%40googlegroups.com.
