On 18 April 2016 at 23:50, Brian Coca <[email protected]> wrote: > We don't keep track of the origin of what goes into ansible_facts. > > > ---------- > Brian Coca > > Which is not what I was suggesting with the 'refresh' idea.
I'm somewhat confused, where you suggesting 'meta: clear_facts' as an alternative, or as the place where the 'refresh' idea should be added? Rather than trying to maintain where facts come from, I was suggesting that if 'refresh' is set, I want what ever is normally gathered to be re-gathered, which would refresh that set of facts without discarding any of the the additional facts that were previously returned by other modules and saved to the fact cache. The 'clear_facts' would be useful in some cases for us as well, just slightly different, as it would wipe out everything all the time which isn't desirable. https://github.com/electrofelix/ansible/commit/ed7fef10da00e36835e89f4954b8132d28b6e183 looks like it would be sufficient, I just haven't tested it properly yet. -- Darragh Bailey "Nothing is foolproof to a sufficiently talented fool" -- 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/CACR765_MO%3DbUz5F_udFAPcXG9sFb4YNsN43RF%2Be91tVsiPRHoA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
