https://c2platform.org/tags/import_tasks/Recent content in Import_tasks on C2 PlatformHugoenhttps://c2platform.org/docs/guidelines/coding/import-unless/Mon, 01 Jan 0001 00:00:00 +0000https://c2platform.org/docs/guidelines/coding/import-unless/<div class="alert alert-primary" role="alert"> Prefer static reuse in Ansible. Use <code>import_tasks</code>, <code>import_role</code>, or the play-level <code>roles</code> section by default. Use <code>include_tasks</code> or <code>include_role</code> only when you need dynamic runtime behavior such as looping, runtime file selection, or conditional inclusion based on facts or earlier task results. </div> <h2 id="problem">Problem</h2> <p>Ansible offers both <code>import_*</code> and <code>include_*</code> forms for reusing tasks and roles.</p> <p>Without a clear rule, codebases drift into a mixture of static and dynamic reuse. That makes playbooks harder to read, reason about, and troubleshoot. Tasks may no longer appear clearly in <code>--list-tasks</code>, tags may behave unexpectedly, and execution can depend on runtime state in ways that are harder for reviewers and operators to see up front.</p>