{"id":1212,"date":"2026-05-20T09:09:07","date_gmt":"2026-05-20T09:09:07","guid":{"rendered":"https:\/\/techno.slomka.biz\/?p=1212"},"modified":"2026-05-20T09:09:37","modified_gmt":"2026-05-20T09:09:37","slug":"deep-dive-mastering-the-missing-file-trap","status":"publish","type":"post","link":"https:\/\/techno.slomka.biz\/?p=1212","title":{"rendered":"Deep Dive: Mastering the “Missing File Trap”"},"content":{"rendered":"\n

This is a follow up to my previous post Mastering Dynamic Task Includes in Ansible<\/a>.<\/p>\n\n\n\n

Because include_tasks<\/code> evaluates variables at runtime<\/strong> (right when the play reaches that specific step), Ansible has no idea whether the target file actually exists when the playbook first starts.<\/p>\n\n\n\n

If a user passes a typo like action=instal<\/code> instead of install<\/code>, Ansible will execute every task right up to your include step, and then crash with a fatal “file not found” error.<\/p>\n\n\n\n

To prevent this, we use the with_first_found<\/code> lookup plugin. It scans a list of files sequentially and includes the first one<\/strong> it actually finds on disk. By designing a deliberate fallback strategy, default_action.yml<\/code> can become an active operational tool.<\/p>\n\n\n\n

Scenario 1: The “Always Run” Setup<\/h2>\n\n\n\n

If there are foundational tasks that must<\/em> happen regardless of the specific action, you can use the fallback file to execute them, ensuring your playbook remains stable.<\/p>\n\n\n\n

YAML<\/span>