Files identified in the description:

• lib/ansible/modules/utilities/logic/debug.py

If these files are inaccurate, please update the component name section of the description or use the !component bot command.

click here for bot help

cc @dagwieers
click here for bot help

@valerio-gr The whole item is added to the module result (which is a case for all modules, not just debug) whether loop label is set or not, the thing that changes with loop label set is this ok: [localhost] => (item=server1) => { - only item.name is listed here and not the whole item. I don't think this is a bug.

@mkrizek, Isn't that a bug?
The result should just be the output of the msg variable and not include the item itself.
Note: this example is taken pretty much straight from Ansible documentation as an example to limit what is going to be displayed but I still have the whole item displayed.

@mkrizek,
if that's not considered a bug. Can I change this to a Feature Request?
Maybe have a debug or loop control option to set (e.g. quiet: yes) to avoid the printout on screen of the item.
Basically what is printed on screen, should just be the content of the msg variable and not the items through which the loop is done (that can be include in msg if required btw).

testing your playbook with PR above:

ok: [localhost] => (item=server1) => {
    "msg": "server1"
}
ok: [localhost] => (item=server1) => {
    "msg": "server2"
}
ok: [localhost] => (item=server1) => {
    "msg": "server3"
}

Would be nice to see this in v2.5 though ;-)

Ah I noticed now it is in v2.5 !

merged 10mins ago

i have 2.6.3 and it still shows whole item instead of only one specified variable. maybe i need to specify any additional parameter?

 - hosts: localhost
  tasks:
  - name: obtain login credentials
    include_vars: /etc/ansible/secrets.yml

  - name: Look up for mac on major devices
    register: result
    findmac:
      mod_ip: "{{ hostvars[item]['ansible_host'] }}"
      mod_user: "{{ creds['username'] }}"
      mod_pass: "{{ creds['password'] }}"
      mod_mlookup: "{{ ex_addr }}"
    loop: "{{ groups['admmainswitch'] }}"

  - name: Look up for port on devices
    register: result2
    findport:
      mod_ip: "{{ hostvars[item]['ansible_host'] }}"
      mod_user: "{{ creds['username'] }}"
      mod_pass: "{{ creds['password'] }}"
      mod_lookup: "{{ result['results'][0]['meta']['cisco_msays'] }}"
    loop: "{{ groups['admswitch'] }}"

  - name: Output
    debug:
      msg: "{{ item['meta']['cisco_says'] }}"
    loop: "{{ result2['results'] }}"

@bcoca I still have this problem in 2.7.14. Do i need to add any extra parameter to debug?

Any update on this, I am also getting same issue with 2.6.5

I am also having this issue with 2.6.4.

ansible 2.7.0

I'm still seeing this huge item output:
ok: [node1] => (item={'virtualenv': '/path/to/app', 'changed': True, 'requirements': '/path/to/app/requirements.txt', 'name': None, 'stdout': "Collecting git+http://bitbucket/scm/lib/some_lib.git@v2 (from -r /path/to/app/requirements.txt (line 39))\n Cloning http://bitbucket/scm/lib/some_lib.git (to revision v2) to ./pip-req-build-j8fphy0v\nSwitched to a new branch 'v2'\nBranch v2 set up to track remote branch v2 from origin.\nCollecting git+http://bitbucket/scm/lib/some_lib.git@v3 (from -r /path/to/app/requirements.txt (line 40))\n Cloning http://bitbucket/scm/lib/some_lib.git (to revision v3) to ./pip-req-build-errntcx9\nSwitched to a new branch 'v3'\nBranch v3 set up to track remote branch v3 from origin.\nCollecting git+http://bitbucket/scm/lib/some_lib.git@v1 (from -r /path/to/app/requirements.txt (line 41))\n Cloning http://bitbucket/scm/lib/some_lib.git (to revision v1) to ./pip-req-build-m_xq_o34\nSwitched to a new branch 'v1'\nBranch v1 set up to track remote branch v1 from origin.\nCollecting git+http:/

when running this handler:
- name: Pip - requirements output debug: msg: - "{{ item.stdout.split('\n') }}" listen: requirements with_items: - "{{ requirements }}"

Not seeing any good method for cleaning this output up and it takes up many lines in stdout, is there a solution that already exists or is that part of this issue?

@AngryNorseMan I use:

no_log: True

But I think it should, by default, not show all that verbose output.

@AngryNorseMan: ansible 2.7.0

I'm still seeing this huge item output:

Same here and it was driving me bonkers. I couldn't seem to figure out why the deeply nested variable structure was printing above just the value I wanted to see via the debug module.

Like your example, I'm still using with_items as that is what I've gotten used to.

According to #47679, it appears that a custom loop label can be used along with the loop keyword to control the level of output. This seems to take care of the specific problem noted on this issue.

More info here:

https://docs.ansible.com/ansible/latest/user_guide/playbooks_loops.html

EDIT: I just realized that much of what I noted here is listed in the OP. I missed that when searching via Google and landing here.

Adding a note for future visitors, make sure you use debug with msg and not var.