Repository navigation
Ansible Names
Alex Willmer edited this page Jul 27, 2026
·
2 revisions
Ansible plugins (e.g. Ansible modules) each have a Fully Qualified Collection Name (FQCN). Each plugtin type is a distinct namespace - the collection acme.example can have a module acme.example.foo, a filter called acme.example.foo, and a test called acme.example.foo. Built-in plugins are mapped to a special collection by the loading mechanism.
Many plugins are implemented as a Python module, which has a distinct fully qualified name (aka fullname) within Python. The Ansible FQCN usually won't match the Python fully qualified name and the Python fully qualified name may differ on the controller and the target.
| Ansible FQCN | Python FQN/fullname | Relative file path | |
|---|---|---|---|
| ansible.builtin.ping | ansible.modules.dnf | .../ansible/modules/dnf.py | |
| amazon.aws.route53 | ansible_collections.amazon.aws.plugins.modules.route53 | .../ansible_collections/amazon/aws/plugins/modules/route53.py |
| Ansible FQCN | Python FQN/fullname | Relative file path |
|---|---|---|
| ??? | ansible.module_utils.basic | .../ansible/module_utils/basic.py |
| ??? | ansible_collections.amazon.aws.plugins.module_utils.botocore | .../ansible_collections/amazon/aws/plugins/module_utils/botocore.py |