# INJECT\_FACTS\_AS\_VARS is defaulting to False in 2.24

**URL:** <https://forum.ansible.com/t/inject-facts-as-vars-is-defaulting-to-false-in-2-24/44886>\
**Category:** Get Help\
**Tags:** ansible-core\
**Created:** [November 23, 2025, 9:09am UTC](https://forum.ansible.com/t/inject-facts-as-vars-is-defaulting-to-false-in-2-24/44886 "2025-11-23T09:09:08Z")\
**Posts on this page:** 1\
**Showing post:** 31

<div class="post-metadata">

**Author:** ![bcoca](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/bcoca/32/9269_2.png) [@bcoca](https://forum.ansible.com/u/bcoca)\
**Post date:** [January 12, 2026, 7:31pm UTC](https://forum.ansible.com/t/inject-facts-as-vars-is-defaulting-to-false-in-2-24/44886/31 "2026-01-12T19:31:53Z")

</div>

> [@utoddl](#):
>
> Understood, but nobody cares that the default of a setting nobody has ever looked at is changing. What they care about what they need to look for to make the warning go away before errors start happening. Otherwise it may as well say “Useless purple text, but you only get one copy per run - lucky you.”

Replacing variable access is not the only solution, the much simpler one is setting the value explicitly in configuration. That is the main reason for this warning. Yes, moving to `ansible_facts` is preferable in the long run as ‘injection’ creates many issues for a very small convenience, why we also add that as an option in the warning.

---

_[View the full topic](https://forum.ansible.com/t/inject-facts-as-vars-is-defaulting-to-false-in-2-24/44886)._