What is the “ansible.builtin” Ansible collection? What is the “ansible.legacy” collection? Today we’re going to talk about Ansible’s most essential modules and plugins and how we can use them in our everyday Playbook. I’m Luca Berton, Ansible Automation Expert, and welcome to today’s lesson.

What is ansible.builtin collection?

The “ansible.builtin” collection refers to modules & plugins shipped with ansible-core. Technically is a synthetic collection, virtually constructed by the core engine.

What is ansible.legacy collection?

The “ansible.legacy” collection is a superset of “ansible.builtin” with ‘custom’ plugins in the configured paths and adjacent directories. We use the “ansible.legacy” when we don’t specify any Ansible collection in our playbook. Technically is a synthetic collection, virtually constructed by the core engine.

Demo

Live Playbook about “ansible.builtin” vs. “ansible.legacy” collections. Let’s jump in a quick Playbook to demonstrate the difference between the “ansible.builtin” vs. “ansible.legacy” collections. I’m going to create a custom “debug” module that prints the extra text “foo” when used with the “msg” parameter. Let’s see the different results when we execute with “ansible.builtin”, “ansible.legacy” or without specifying any collections. The code is the following.

common code

  • inventory (localhost)
localhost ansible_connection=local
  • ansible.cfg
[defaults]
action_plugins = plugins/action
  • plugins/action/debug.py
# Copyright 2012, Dag Wieers <[email protected]>
# Copyright 2016, Toshio Kuratomi <[email protected]>
#
# This file is part of Ansible
#
# Ansible is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 3 of the License, or
# (at your option) any later version.
#
# Ansible is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with Ansible.  If not, see <http://www.gnu.org/licenses/>.
from __future__ import (absolute_import, division, print_function)
__metaclass__ = type

from ansible.errors import AnsibleUndefinedVariable
from ansible.module_utils.six import string_types
from ansible.module_utils._text import to_text
from ansible.plugins.action import ActionBase

class ActionModule(ActionBase):
    ''' Print statements during execution '''

    TRANSFERS_FILES = False
    _VALID_ARGS = frozenset(('msg', 'var', 'verbosity'))

    def run(self, tmp=None, task_vars=None):
        if task_vars is None:
            task_vars = dict()

        validation_result, new_module_args = self.validate_argument_spec(
            argument_spec={
                'msg': {'type': 'raw', 'default': 'Hello world!'},
                'var': {'type': 'raw'},
                'verbosity': {'type': 'int', 'default': 0},
            },
            mutually_exclusive=(
                ('msg', 'var'),
            ),
        )

        result = super(ActionModule, self).run(tmp, task_vars)
        del tmp  # tmp no longer has any effect

        # get task verbosity
        verbosity = new_module_args['verbosity']

        if verbosity <= self._display.verbosity:
            if new_module_args['var']:
                try:
                    results = self._templar.template(new_module_args['var'], convert_bare=True, fail_on_undefined=True)
                    if results == new_module_args['var']:
                        # if results is not str/unicode type, raise an exception
                        if not isinstance(results, string_types):
                            raise AnsibleUndefinedVariable
                        # If var name is same as result, try to template it
                        results = self._templar.template("{{" + results + "}}", convert_bare=True, fail_on_undefined=True)
                except AnsibleUndefinedVariable as e:
                    results = u"VARIABLE IS NOT DEFINED!"
                    if self._display.verbosity > 0:
                        results += u": %s" % to_text(e)

                if isinstance(new_module_args['var'], (list, dict)):
                    # If var is a list or dict, use the type as key to display
                    result[to_text(type(new_module_args['var']))] = results
                else:
                    result[new_module_args['var']] = results
            else:
                result['msg'] = (new_module_args['msg'] + "foo")

            # force flag to make debug output module always verbose
            result['_ansible_verbose_always'] = True
        else:
            result['skipped_reason'] = "Verbosity threshold not met."
            result['skipped'] = True

        result['failed'] = False

        return result

ansible.builtin code

  • ansible.builtin.yml
---
- name: debug module Playbook
  hosts: all
  vars:
    fruit: "apple"
  tasks:
    - name: Builtin
      ansible.builtin.debug:
        msg: "{{ fruit }}"

ansible.builtin execution

$ ansible-playbook -i inventory ansible.builtin.yml

PLAY [debug module Playbook] ****************************************************************

TASK [Gathering Facts] ******************************************************************
ok: [localhost]

TASK [Builtin] **************************************************************************
ok: [localhost] => {
    "msg": "apple"
}

PLAY RECAP ******************************************************************************
localhost                  : ok=2    changed=0    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0

ansible.legacy code

  • ansible.legacy.yml
---
- name: debug module Playbook
  hosts: all
  vars:
    fruit: "apple"
  tasks:
    - name: Legacy
      ansible.legacy.debug:
        msg: "{{ fruit }}"

ansible.legacy execution

$ ansible-playbook -i inventory ansible.legacy.yml 

PLAY [debug module Playbook] ****************************************************************

TASK [Gathering Facts] ******************************************************************
ok: [localhost]

TASK [Legacy] ***************************************************************************
ok: [localhost] => {
    "msg": "applefoo"
}

PLAY RECAP ******************************************************************************
localhost                  : ok=2    changed=0    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0

ansible.vanilla code

  • ansible.vanilla.yml
---
- name: debug module Playbook
  hosts: all
  vars:
    fruit: "apple"
  tasks:
    - name: Vanilla
      debug:
        msg: "{{ fruit }}"

ansible.legacy execution

$ ansible-playbook -i inventory ansible.vanilla.yml 

PLAY [debug module Playbook] ****************************************************************

TASK [Gathering Facts] ******************************************************************
ok: [localhost]

TASK [Vanilla] **************************************************************************
ok: [localhost] => {
    "msg": "applefoo"
}

PLAY RECAP ******************************************************************************
localhost                  : ok=2    changed=0    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0

Conclusion

Now you know more about the “ansible.builtin” and the “ansible.legacy” collections. This is a great foundation for your Ansible Playbook onward. Subscribe to the YouTube channel, Medium, and Website, X (formerly Twitter) to not miss the next episode of the Ansible Pilot.

Academy

Learn the Ansible automation technology with some real-life examples in my Udemy 300+ Lessons Video Course.

BUY the Complete Udemy 300+ Lessons Video Course

My book Ansible By Examples: 200+ Automation Examples For Linux and Windows System Administrator and DevOps

BUY the Complete PDF BOOK to easily Copy and Paste the 250+ Ansible code

Want to keep this project going? Please donate

Patreon Buy me a Pizza