From 6f1fd12265336818c68464e16cebbbfeb9850af1 Mon Sep 17 00:00:00 2001
From: Matthew Mosesohn <mmosesohn@mirantis.com>
Date: Fri, 8 Sep 2017 10:19:58 +0300
Subject: [PATCH] Revert "Add option for fact cache expiry" (#1636)

* Revert "Add option for fact cache expiry (#1602)"

This reverts commit fb30f659516d55e2494561a2008d1d9e6a16b3ed.
---
 ansible.cfg | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/ansible.cfg b/ansible.cfg
index 6ec3c35bc..aecb198a0 100644
--- a/ansible.cfg
+++ b/ansible.cfg
@@ -7,9 +7,6 @@ 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