On Thursday, October 19, 2017 at 3:11:17 PM UTC+2, Toshio Kuratomi wrote: > > > Cache invalidation is one of programming's harder problems. So, solve the > git version problem but ignore the urge to cache your results for now. > > -toshio >
That's true, and ansible is already caching a good deal of information subject to change - for example logical volume sizes which can change automatically outside of ansible control - e.g. thin-pool or snapshot can grow when over threshold, and it is strongly recommended to set it up that way for thin-pools. So I wonder if it would be a good idea to have an implicit "notify" for updated packages. For updates outside of ansible control - there is a space for TOCTOU race anyway. Also in this particular case, when git does not support includes, the whole configuration must take that into account, and better there are no includes to rely upon. So I am prone to think it would be an improvement to have that flag in facts and available globally. And the next thing: to use git_config, the git must be installed, so it is most likely preceded by an equivalent of `package: name=git state=present`. -- Martian -- 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/aa9fbb0b-7f86-4241-a81d-368b52adea5a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
