From fb30f659516d55e2494561a2008d1d9e6a16b3ed Mon Sep 17 00:00:00 2001
From: Yorgos Saslis <g.saslis@gmail.com>
Date: Thu, 7 Sep 2017 23:29:27 +0300
Subject: [PATCH] Add option for fact cache expiry (#1602)

* Add option for fact cache expiry

By adding the `fact_caching_timeout` we avoid having really stale/invalid data ending up in there.
Leaving commented out by default, for backwards compatibility, but nice to have there.

* Enabled cache-expiry by default

Set to 2 hours and modified comment to reflect change
---
 ansible.cfg | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/ansible.cfg b/ansible.cfg
index aecb198a0..6ec3c35bc 100644
--- a/ansible.cfg
+++ b/ansible.cfg
@@ -7,6 +7,9 @@ host_key_checking=False
 gathering = smart
 fact_caching = jsonfile
 fact_caching_connection = /tmp
+# Once created, fact cache is never force updated. This is why the tiemeout exists. If you're still getting 
+# stale data in your runs (e.g. stale `etcd_access_addresses`), you might want to use `--flush-cache`. 
+fact_caching_timeout = 7200 # 2 hours
 stdout_callback = skippy
 library = ./library
 callback_whitelist = profile_tasks
-- 
GitLab