Add caution about handlers & import to Pitfalls (#61060)

* Add caution about handlers & import to Pitfalls on the playbooks_reuse page.
The fact that handlers lose their name: when using import_tasks:, while logical, is not intuitive and should be noted.
Co-Authored-By: Sandra McCann <samccann@redhat.com>
pull/61887/head
Christopher Engelhard 5 years ago committed by Alicia Cozine
parent ce8af1c8c5
commit 375eb9723a

@ -63,6 +63,7 @@ Using ``import*`` can also have some limitations when compared to dynamic includ
* As noted above, loops cannot be used with imports at all. * As noted above, loops cannot be used with imports at all.
* When using variables for the target file or role name, variables from inventory sources (host/group vars, etc.) cannot be used. * When using variables for the target file or role name, variables from inventory sources (host/group vars, etc.) cannot be used.
* Handlers using ``import*`` will not be triggered when notified by their name, as importing overwrites the handler's named task with the imported task list.
.. note:: .. note::
Regarding the use of ``notify`` for dynamic tasks: it is still possible to trigger the dynamic include itself, which would result in all tasks within the include being run. Regarding the use of ``notify`` for dynamic tasks: it is still possible to trigger the dynamic include itself, which would result in all tasks within the include being run.

Loading…
Cancel
Save