From 375eb9723aed60b121531a4b5134f50fada465ba Mon Sep 17 00:00:00 2001 From: Christopher Engelhard Date: Thu, 5 Sep 2019 21:18:09 +0200 Subject: [PATCH] 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 --- docs/docsite/rst/user_guide/playbooks_reuse.rst | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/docsite/rst/user_guide/playbooks_reuse.rst b/docs/docsite/rst/user_guide/playbooks_reuse.rst index 310644830e4..cd527ad18ca 100644 --- a/docs/docsite/rst/user_guide/playbooks_reuse.rst +++ b/docs/docsite/rst/user_guide/playbooks_reuse.rst @@ -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. * 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:: 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.