On 4 March 2014 14:54, Michael DeHaan <[email protected]> wrote: > I'm saying this works for top level playbooks, and that facts are not > erased between includes: > > > # site.yml > > - hosts: all > gather_facts: yes > tasks: [] > > - include: webserver_plays.yml > - include: dbserver_plays.yml > > > What I have been doing until now as a personal best practice, is always explicitly set gather_facts: true or false on every play, setting it on true in plays where facts are used. This way facts gathering would trigger at the very last when I need them. Now this new behavior will trigger extra runs, burning unneeded cycles.
I should also agree with Brian, I never encountered the key problem that is solved here though. On a dangerous side node, I actually never understood why registered variables and set_fact vars live in the same namespace as gathered facts. Serge -- 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/CAEhzMJAYhndeP3LdQtGwmORthbe_70T8PmOfaKbTzzu12EcM8A%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
