"My thoughts are that leaving it off by default means that almost no-one
will notice it, and I think that will be a shame."
Yep, I share that same concern.
There's a balance there.
There are perhaps ways we could make this more known, like including a note
in the docs for the command module and
My thoughts are that leaving it off by default means that almost no-one
will notice it, and I think that will be a shame.
It's just a warning - Ansible doesn't fail if you use command when a module
exists.
Could we try it in 1.8 devel before release - or will that cause too much
extra traffic
For me, a very good decision :)
--
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-project+unsubscr...@googlegroups.com.
To post to this group, send emai
I believe all the defaults are appropriate for most people.
Smart is debateable, maybe. It depends on what kinds of facts you are
relying on whether regathering is good or bad, but it's easily to manually
control with gather_facts: no, too.
pipelining is the one I'd seriously consider most peopl
Is there a list of options that are off by default, but recommended to be
turned on? This would be one such option, and I think gathering=smart is
another better default.
Michael DeHaan napisał:
>I think I'm going to leave this off by default, in the "no new
>surprises"
>vein.
>
>It's still a v
I think I'm going to leave this off by default, in the "no new surprises"
vein.
It's still a very good feature that I think lots of people will turn on.
On Fri, Aug 22, 2014 at 3:39 PM, Michael DeHaan wrote:
> I just merged in another Will Thames patch that's been in queue for a
> while that
