Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add caution about handlers & import to Pitfalls #61060

Merged
merged 2 commits into from Sep 5, 2019
Merged

Add caution about handlers & import to Pitfalls #61060

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
87c1413
Add caution about handlers & import to Pitfalls
lcts Aug 21, 2019
48a6790
Update playbooks_reuse.rst as suggested
lcts Sep 3, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/docsite/rst/user_guide/playbooks_reuse.rst
View file
Open in desktop
Expand Up @@ -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 via their name, as importing overwrites the handler's named task with the imported task list.
lcts marked this conversation as resolved.
Show resolved Hide resolved

.. 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.
Expand Down