> > Hi > I understand that task-level includes are completely dynamic in 2.0 and therefore the following command / option ( --list-tasks ) can not list tasks in the task-level includes at parse time present in playbookfoo.yml :
ansible-playbook playbookfoo.yml --list-tasks However, I feel that it should at least list the task-level include filenames when using option --list-tasks to indicate that there may or may not be further tasks at runtime. This could provide a better idea of what is actually going on at ansible-playbook runtime. Of course, this depends strongly on how meaningful the task-level include filenames are. Phonthip Namkaew > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/1725ed7f-f2d7-4dd6-ad6c-5a388b9612c2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
