I know that I suggested this, but I really don't see a downside in using *gather_facts: force*. It is simple, seems the easiest to implement, it is easy to read and feels natural. Only downside I see is that gather_facts is a Boolean, and if we allowed "force", it will end being that and might feel a little strange.
On the other hand adding additional options to *setup *module like *ignore_tags *and *ignore_limit *is cool, but what I don't like about it is that you would need to do *gather_facts: False* before that. The same goes for using *setup *with *delegate_to*. Don't get me wrong those additional parameters for the setup module are great ideas and I think Ansible should have them as well, so that you can gather custom facts, but Ansible is always being promoted as being extremely simple and *gather_facts: force/always* is as simple as it can be. On Monday, March 24, 2014 8:20:37 PM UTC+1, Grzegorz Nosek wrote: > > W dniu 24.03.2014 20:02, Brian Coca pisze: > > it would require changing current behavior, now if you do setup + > > delegate_to, you populate 'current' host with delegated host facts. > > Right, my bad. > > Still, I don't really like the target= as a parameter of the setup > module. It complicates the implementation too much IMHO. It effectively > duplicates the whole support of delegate_to with a minor change in > functionality (which I forgot and you pointed out). > > Another play-level option (delegate_facts: true?) might be more > universal and would keep writing custom fact modules trivial. > > Best regards, > Grzegorz Nosek > -- 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/4608a51a-fcbc-4dde-a128-1a1ba2332aa2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
