--
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 ansible-proje...@googlegroups.com.
To post to this group, send email to ansible...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/2bb40eb4-a75d-4280-9332-8faa2f060fba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to a topic in the Google Groups "Ansible Project" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ansible-project/4_UxdmUx3vQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ansible-proje...@googlegroups.com.
To post to this group, send email to ansible...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAFOdRHJhtKDn%3DQ%3DbAsCi2V_bxnaK8a49PiMBqeOFiTaR%2B6fTYQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Since ansible already supports caching of facts shouldn't this also be a job of ansible itself? Otherwise each dynamic inventory plugin will implement it in a different way or not implement it at all...
----------
You've hit the nail on the head! We do have plans to make a 'inventory cache' part of Ansible itself, currently its up to each script and of course we have different implementations and some that don't implement any.