Summary

When running the ansible-playbook command with the --list-tasks option, if tasks are referenced using include_tasks and lack a name value, the output is as shown below (AS-IS). I find this output format to be less visible. It would be better if the names of the referenced files were also displayed.

Issue Type

Feature Idea

Component Name

taskmsg

Additional Information

[AS-IS]

  play #8 (test): test	TAGS: []
    tasks:
      include_tasks	TAGS: [test]
      include_tasks	TAGS: [test]
      include_tasks	TAGS: [test]

[TO-BE]

  play #8 (test): test	TAGS: []
    tasks:
      include_tasks INCLUDE: test1.yml	TAGS: [test]
      include_tasks INCLUDE: test2.yml	TAGS: [test]
      include_tasks INCLUDE: test3.yml	TAGS: [test]

Code of Conduct

• I agree to follow the Ansible Code of Conduct

Files identified in the description:

None

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

the problem with this:

- include_tasks:
          name: '{{variable}}.yml'

the problem with this:

- include_tasks:

          name: '{{variable}}.yml'

If I do as you suggested, it does produce the output I want, but wouldn't it be more visible if the output could be shown even without the ansible author entering the name value?

I was not clear enough, I was posting the case in which the play did not have that variable defined, if it comes from inventory or extra vars or runtime composition in other ways, it won't be available for templating so you cannot show which file, much less which tasks it would include.

I was only referring to the part about the file that import_task refers to. Does it also retrieve the name of the file referenced by import_task at runtime?