I have to say, that it kind of bothers me that fact "caching" is the solution to whether or not it works. Caching is normally about speeding things up or making them more scalable. Not about having it actually be correct. In this instance, wouldn't relying on fact caching break every time the cache is flushed, or on a new system that was not loaded with the cache?
-- Michael Peters On Mon, May 4, 2015 at 9:49 AM, Brian Coca <[email protected]> wrote: > Another way around this is using persistent fact caching. > > -- > Brian Coca > > -- > You received this message because you are subscribed to the Google Groups > "Ansible Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-project/CAJ5XC8kf5An9BvRX%2BUb2Bcw%2BuQ04ZV%3D_rozQAkNqp3BdnmG_Kw%40mail.gmail.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAJQqANcUntwe_2yqbTzS9LzTqJ-Tkdqk0zgo_EgtMpm5BMKseQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
