- action: shell echo {{item}} with_items: - 1 - 2 register: task - debug: var=item.stdout_lines with_items: "{{task.results}}" Ansible debug module is easy to use. A loop (previously known as with_items) is very simple and powerful and allows you to iterate over a list or dictionary in an easy fashion. When you register the result of a loop (e.g. Note. Also, while working in a team where others also have the same stakes as you, using the debug module to add more information is always beneficial and can avoid confusion and dependencies. Ansible Task - name: Report the /boot/initramfs file status for latest installed kernel debug: msg: "{{ ansible_hostname }} = {{INITRAMFS_LAST_KERNEL.stdout}}" Output Many people that use Ansible are very familiar with the loop construct. Despite that, we recommend you use the FQCN for easy linking to the module documentation and to avoid conflicting with other collections that may have the same module name. I have made a minimal example to illustrate the problem. I have displayed variable and message in the debug same task. This module is part of ansible-base and included in all Ansible installations. Getting Started. You do not need to register your result with the item salt. Ansible Debug Module with Examples Ansible debug module is used to print the message in the log output. I've tried using loop|dict2items (the structure isn't a dictionary, & it … Now, I want to checkout repositories and afterwards build docker images only when the source has changed. I want to execute several commands using the "with_items" construct in Ansible. Since getting the source and building the image is the same for all items except the name I created the tasks with with_items: images and try to register the result with: register: "{{ item }}" and also tried. For our first example, let’s try a simple hello world playbook. In the following examples I will show how to use debug module to print variable values, … Note. You can set up the 1_debug_example.yml playbook file: Ansible debug module is a very helpful tool for playbook developers and for administrators who work on need to update a playbook frequently on per need basis. In most cases, you can use the short module name dict even without specifying the collections: keyword. The message is nothing but any variable values or output of any task. If a command failed I want to print its standard output. Debugging tasks¶ Ansible offers a task debugger so you can fix errors during execution instead of editing your playbook and running it again to see if your change worked. the output in 1.9.4 means that ansible could not find the var [('a', 1), ('b', 2)] so it equates it to itself, in 2.0 this would be undefined, but debug is now smart enough to see a list and print it. In most cases, you can use the short module name fail even without specifying the collections: keyword. I am new to Ansible and I am trying to create several virtual environments (one for each project, the list of projects being defined in a variable). Let us … Despite that, we recommend you use the FQCN for easy linking to the module documentation and to avoid conflicting with other collections that may have the same module name. with_items) the registered value will contain a key results which holds a list of all results of the loop. However, I find that many people are not aware of the until loop. Instead of looping over your original device list, you can loop over the registered results of … (See docs). register: "src_{{ item }}" This module is part of ansible-base and included in all Ansible installations. I'm getting different results when using loop vs with_items when trying to iterate over a list of dictionaries. You have access to all of the features of the debugger in the context of the task.