0Pricing
Ansible Academy · Lesson

Using FQCN: namespace.collection.module

Reference content the modern way.

Using FQCN: namespace.collection.module is a free Ansible Academy lesson on CoddyKit — lesson 3 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Ansible Academy learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.

Short Names Are Ambiguous

Calling a module just copy works, but two collections could each ship a copy. The FQCN removes any doubt about which one you mean.

FQCN Spelled Out

FQCN means Fully Qualified Collection Name: the full address of a module written as namespace.collection.module.

Three Parts, One Dot Path

Read it left to right: the namespace (owner), the collection (package), then the module. Each piece narrows down exactly what runs.

ansible.builtin.copy
# namespace.collection.module

Core Lives in ansible.builtin

The classic modules you already use sit in the ansible.builtin collection. So copy is really ansible.builtin.copy under the hood.

- ansible.builtin.copy:
    src: app.conf
    dest: /etc/app.conf

Why It Became the Default

Since modules now live in many collections, the FQCN is the only name guaranteed to resolve to the exact module every time.

Community Modules Look the Same

Content from other packages follows the same pattern, like community.general.ufw for the firewall module in that collection.

- community.general.ufw:
    rule: allow
    port: "22"

Short Names Still Work

Plain names like copy remain valid for builtin modules, but linters now warn you. Using the full FQCN is the recommended style.

Future-Proofs Your Playbooks

An FQCN keeps working even if a future Ansible reshuffles where short names point, so your plays stay stable across upgrades.

FQCNs Apply to Roles Too

Collections ship roles as well. You reference them with the same dotted address, like community.general.role_name in your play.

roles:
  - role: geerlingguy.nginx

Cut Typing with collections

List a collection under the play's collections key and you may then use short module names from it without the full prefix.

collections:
  - community.general

Make FQCN a Habit

Writing the full FQCN from the start makes playbooks unambiguous, lint-clean, and easy for teammates to trace to a source.

Quick Check

Identify the parts of a fully qualified module name.

Recap

An FQCN is namespace.collection.module, like ansible.builtin.copy. It points unambiguously at one module and keeps playbooks upgrade-safe. 🎯

Frequently asked questions

Is the “Using FQCN: namespace.collection.module” lesson free?

Yes — the full text of “Using FQCN: namespace.collection.module” is free to read here on the web, and the Ansible Academy course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Ansible Academy course, upgrade to CoddyKit PRO.

What will I learn in “Using FQCN: namespace.collection.module”?

Reference content the modern way. You practise Ansible Academy with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.

Do I need any experience to start Ansible Academy?

No prior experience is required. Ansible Academy on CoddyKit is structured for beginners through advanced learners; this is — lesson 3 of 4, so you can start here or from the beginning and move at your own pace.

How long does the “Using FQCN: namespace.collection.module” lesson take?

Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.

Can I write and run code in this Ansible Academy lesson?

Yes. Every Ansible Academy lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.

All lessons in this course

  1. Roles vs Collections on Galaxy
  2. Install Roles with requirements.yml
  3. Using FQCN: namespace.collection.module
  4. Publishing Your Own Role to Galaxy
← Back to Ansible Academy