<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Include_tasks on Computing Arts</title>
    <link>https://computingarts.com/tags/include_tasks/</link>
    <description>Recent content in Include_tasks on Computing Arts</description>
    <generator>Hugo -- 0.146.0</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 15 Apr 2026 14:00:00 -0400</lastBuildDate>
    <atom:link href="https://computingarts.com/tags/include_tasks/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Why Ansible include_tasks Variables Are Not Defined in the Parent Play</title>
      <link>https://computingarts.com/posts/2026-04-15-ansible-include-tasks-variable-not-defined/</link>
      <pubDate>Wed, 15 Apr 2026 14:00:00 -0400</pubDate>
      <guid>https://computingarts.com/posts/2026-04-15-ansible-include-tasks-variable-not-defined/</guid>
      <description>&lt;h1 id=&#34;why-ansible-include_tasks-variables-are-not-defined-in-the-parent-play&#34;&gt;Why Ansible &lt;code&gt;include_tasks&lt;/code&gt; Variables Are Not Defined in the Parent Play&lt;/h1&gt;
&lt;p&gt;You define a variable inside an &lt;code&gt;include_tasks&lt;/code&gt; file. The task runs successfully. Then the very next task in your parent play fails with &lt;code&gt;variable is undefined&lt;/code&gt;. What just happened?&lt;/p&gt;
&lt;p&gt;This is one of the most confusing Ansible behaviors, and it bites people repeatedly because it looks like a bug. It&amp;rsquo;s not — it&amp;rsquo;s a scoping decision — but understanding &lt;em&gt;why&lt;/em&gt; it works this way helps you fix it fast.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
