You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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?
Summary
When running the ansible-playbook command with the --list-tasks option, if tasks are referenced using
include_tasks
and lack aname
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]
[TO-BE]
Code of Conduct
The text was updated successfully, but these errors were encountered: