We've discussed this and what we want to do with gather_facts is make a config setting
gather_facts_tendancy: always or lazy, default always and then if you want to force when it's lazy, you could just call the '- setup' module in the tasks section. On Fri, Mar 14, 2014 at 12:28 PM, Strahinja Kustudić <[email protected]>wrote: > I know this is now and old topic, but it didn't make sense to open a new > one. > > Having offline cache would be nice, but wouldn't be easier to make > something like: > > *gather_facts: force* or *gather_facts_**force: True* > > or something similar, so that this overrides --limit / --tags and always > gathers facts. > > > On Monday, January 13, 2014 5:59:22 PM UTC+1, Brian Coca wrote: >> >> implementing the offline caches might solve this as most host data should >> be available from previous runs. >> > -- > 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/47b5edb1-1f1d-4f70-a5bf-beae4ca0741e%40googlegroups.com<https://groups.google.com/d/msgid/ansible-project/47b5edb1-1f1d-4f70-a5bf-beae4ca0741e%40googlegroups.com?utm_medium=email&utm_source=footer> > . > 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/CAEVJ8QO0FeRzz2Qnue1txD2Bb42dUrM13WcbnnF%3DUUikjvNtvg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
