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
Generic "include" at playbook level exists only for historical reasons and the use of explicit import_playbook should be recommeded.
Issue Type
Feature Idea
Additional Information
Main reasoning for this is because include was also used at tasks level and it causes confusions, that ones are also replace by import_tasks and include_tasks, which well defined behaviors.
This discussion was converted from issue #1073 on June 04, 2021 13:40.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Summary
Generic "include" at playbook level exists only for historical reasons and the use of explicit
import_playbook
should be recommeded.Issue Type
Additional Information
Main reasoning for this is because
include
was also used at tasks level and it causes confusions, that ones are also replace byimport_tasks
andinclude_tasks
, which well defined behaviors.Beta Was this translation helpful? Give feedback.
All reactions