# INJECT\_FACTS\_AS\_VARS is defaulting to False in 2.24 **URL:** \ **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:** 33
**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 13, 2026, 9:44pm UTC](https://forum.ansible.com/t/inject-facts-as-vars-is-defaulting-to-false-in-2-24/44886/33 "2026-01-13T21:44:07Z")
I’m not trying to force it, just moving to a saner default as the injection uses a lot more memory and cpu time, aside from creating possible collisions and security issues. This will incentivize new content to not rely on it. That said, I agree, there should be simpler ways of identifying where the variables are used, your PR goes a long way for that, my fear is warning spam and we are looking at a way to address that. As an aside, what i really want to do in the end is add better introspection in general, being able to list what vars are used where and from what origin for a play/role. But that is a much taller order. --- _[View the full topic](https://forum.ansible.com/t/inject-facts-as-vars-is-defaulting-to-false-in-2-24/44886)._