🧠 𝗔𝗻𝘀𝗶𝗯𝗹𝗲 𝗙𝗮𝗰𝘁𝘀: 𝗧𝗵𝗲 𝗛𝗶𝗱𝗱𝗲𝗻 𝗣𝗼𝘄𝗲𝗿 𝗕𝗲𝗵𝗶𝗻𝗱 𝗦𝗺𝗮𝗿𝘁 𝗔𝘂𝘁𝗼𝗺𝗮𝘁𝗶𝗼𝗻 🧠

If you're using Ansible for automation, you're probably writing tasks. But are you making them intelligent?

That’s where Facts come in — dynamic, real-time system data automatically gathered by Ansible from your managed nodes. ✅

Here’s a quick breakdown 👇

🔍 𝗪𝗵𝗮𝘁 𝗔𝗿𝗲 𝗙𝗮𝗰𝘁𝘀 𝗶𝗻 𝗔𝗻𝘀𝗶𝗯𝗹𝗲?
Facts are key-value data collected at the start of a playbook run via the setup module. They include:

𝟭. 𝗢𝗦 𝗳𝗮𝗺𝗶𝗹𝘆, 𝗱𝗶𝘀𝘁𝗿𝗼, 𝗮𝗻𝗱 𝘃𝗲𝗿𝘀𝗶𝗼𝗻
𝟮. 𝗜𝗣 𝗮𝗱𝗱𝗿𝗲𝘀𝘀𝗲𝘀 𝗮𝗻𝗱 𝗶𝗻𝘁𝗲𝗿𝗳𝗮𝗰𝗲𝘀
𝟯. 𝗛𝗼𝘀𝘁𝗻𝗮𝗺𝗲𝘀
𝟰. 𝗗𝗶𝘀𝗸 𝘀𝗽𝗮𝗰𝗲, 𝗺𝗲𝗺𝗼𝗿𝘆, 𝗖𝗣𝗨 𝗶𝗻𝗳𝗼
𝟱. 𝗡𝗲𝘁𝘄𝗼𝗿𝗸 𝗱𝗲𝘁𝗮𝗶𝗹𝘀

⚙️ 𝗪𝗵𝘆 𝗧𝗵𝗲𝘆 𝗠𝗮𝘁𝘁𝗲𝗿
With Facts, you can:
✔️ 𝘞𝘳𝘪𝘵𝘦 𝘤𝘰𝘯𝘥𝘪𝘵𝘪𝘰𝘯𝘢𝘭 𝘵𝘢𝘴𝘬𝘴 𝘣𝘢𝘴𝘦𝘥 𝘰𝘯 𝘖𝘚, 𝘥𝘪𝘴𝘬, 𝘰𝘳 𝘮𝘦𝘮𝘰𝘳𝘺
✔️ 𝘋𝘺𝘯𝘢𝘮𝘪𝘤𝘢𝘭𝘭𝘺 𝘢𝘴𝘴𝘪𝘨𝘯 𝘱𝘢𝘤𝘬𝘢𝘨𝘦𝘴, 𝘱𝘢𝘵𝘩𝘴, 𝘰𝘳 𝘴𝘦𝘵𝘵𝘪𝘯𝘨𝘴
✔️ 𝘙𝘦𝘥𝘶𝘤𝘦 𝘩𝘢𝘳𝘥𝘤𝘰𝘥𝘪𝘯𝘨 𝘢𝘯𝘥 𝘪𝘮𝘱𝘳𝘰𝘷𝘦 𝘱𝘰𝘳𝘵𝘢𝘣𝘪𝘭𝘪𝘵𝘺
✔️ 𝘈𝘶𝘵𝘰𝘮𝘢𝘵𝘪𝘤𝘢𝘭𝘭𝘺 𝘢𝘥𝘢𝘱𝘵 𝘱𝘭𝘢𝘺𝘣𝘰𝘰𝘬𝘴 𝘵𝘰 𝘥𝘪𝘧𝘧𝘦𝘳𝘦𝘯𝘵 𝘦𝘯𝘷𝘪𝘳𝘰𝘯𝘮𝘦𝘯𝘵𝘴

💡 𝗥𝗲𝗮𝗹-𝗪𝗼𝗿𝗹𝗱 𝗘𝘅𝗮𝗺𝗽𝗹𝗲𝘀
👉 𝗣𝗿𝗶𝗻𝘁 𝘁𝗵𝗲 𝗢𝗦 𝗳𝗮𝗺𝗶𝗹𝘆:
- 𝘯𝘢𝘮𝘦: 𝘚𝘩𝘰𝘸 𝘖𝘚 𝘧𝘢𝘮𝘪𝘭𝘺
𝘥𝘦𝘣𝘶𝘨:
𝘷𝘢𝘳: 𝘢𝘯𝘴𝘪𝘣𝘭𝘦_𝘧𝘢𝘤𝘵𝘴['𝘰𝘴_𝘧𝘢𝘮𝘪𝘭𝘺']
👉 𝗖𝗼𝗻𝗱𝗶𝘁𝗶𝗼𝗻𝗮𝗹 𝗶𝗻𝘀𝘁𝗮𝗹𝗹𝗮𝘁𝗶𝗼𝗻:
- 𝘯𝘢𝘮𝘦: 𝘐𝘯𝘴𝘵𝘢𝘭𝘭 𝘸𝘦𝘣 𝘴𝘦𝘳𝘷𝘦𝘳 𝘣𝘢𝘴𝘦𝘥 𝘰𝘯 𝘖𝘚
𝘱𝘢𝘤𝘬𝘢𝘨𝘦:
𝘯𝘢𝘮𝘦: "{{ '𝘩𝘵𝘵𝘱𝘥' 𝘪𝘧 𝘢𝘯𝘴𝘪𝘣𝘭𝘦_𝘧𝘢𝘤𝘵𝘴['𝘰𝘴_𝘧𝘢𝘮𝘪𝘭𝘺'] == '𝘙𝘦𝘥𝘏𝘢𝘵' 𝘦𝘭𝘴𝘦 '𝘯𝘨𝘪𝘯𝘹' }}"
𝘴𝘵𝘢𝘵𝘦: 𝘱𝘳𝘦𝘴𝘦𝘯𝘵```
👉 𝗔𝗰𝗰𝗲𝘀𝘀𝗶𝗻𝗴 𝗜𝗣 𝗮𝗱𝗱𝗿𝗲𝘀𝘀:
- 𝘯𝘢𝘮𝘦: 𝘗𝘳𝘪𝘯𝘵 𝘱𝘳𝘪𝘮𝘢𝘳𝘺 𝘐𝘗
𝘥𝘦𝘣𝘶𝘨:
𝘷𝘢𝘳: 𝘢𝘯𝘴𝘪𝘣𝘭𝘦_𝘧𝘢𝘤𝘵𝘴['𝘥𝘦𝘧𝘢𝘶𝘭𝘵_𝘪𝘱𝘷4']['𝘢𝘥𝘥𝘳𝘦𝘴𝘴']
👉 𝗦𝗸𝗶𝗽 𝗮 𝘁𝗮𝘀𝗸 𝗼𝗻 𝘃𝗶𝗿𝘁𝘂𝗮𝗹 𝗺𝗮𝗰𝗵𝗶𝗻𝗲𝘀:
- 𝘯𝘢𝘮𝘦: 𝘖𝘯𝘭𝘺 𝘳𝘶𝘯 𝘰𝘯 𝘱𝘩𝘺𝘴𝘪𝘤𝘢𝘭 𝘮𝘢𝘤𝘩𝘪𝘯𝘦𝘴
𝘴𝘩𝘦𝘭𝘭: 𝘦𝘤𝘩𝘰 "𝘙𝘶𝘯𝘯𝘪𝘯𝘨 𝘰𝘯 𝘩𝘢𝘳𝘥𝘸𝘢𝘳𝘦"
𝘸𝘩𝘦𝘯: 𝘢𝘯𝘴𝘪𝘣𝘭𝘦_𝘧𝘢𝘤𝘵𝘴['𝘷𝘪𝘳𝘵𝘶𝘢𝘭𝘪𝘻𝘢𝘵𝘪𝘰𝘯_𝘳𝘰𝘭𝘦'] == '𝘩𝘰𝘴𝘵'

⚡ 𝗣𝗿𝗼 𝗧𝗶𝗽𝘀
💡 𝗗𝗶𝘀𝗮𝗯𝗹𝗲 𝗳𝗮𝗰𝘁 𝗴𝗮𝘁𝗵𝗲𝗿𝗶𝗻𝗴 𝗶𝗳 𝗻𝗼𝘁 𝗻𝗲𝗲𝗱𝗲𝗱:

```𝘨𝘢𝘵𝘩𝘦𝘳_𝘧𝘢𝘤𝘵𝘴: 𝘧𝘢𝘭𝘴𝘦```

💡 Use fact caching (Redis, JSON) for large inventories to speed up execution.
💡 Custom facts can be created in /etc/ansible/facts.d/ as .json or .ini files.

📚 𝗠𝗼𝗿𝗲 𝗼𝗻 𝗔𝗻𝘀𝗶𝗯𝗹𝗲 𝗙𝗮𝗰𝘁𝘀 𝗶𝗻 𝘁𝗵𝗲 𝗼𝗳𝗳𝗶𝗰𝗶𝗮𝗹 𝗱𝗼𝗰𝘀:
🔗 https://lnkd.in/guYUCj7W

Facts aren't just metadata — they're the key to writing context-aware, adaptive, and production-ready playbooks. 🔐