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 <[email protected]> wrote: > I just merged in another Will Thames patch that's been in queue for a > while that reports when certain apparently trivial usage of shell/command > could be better represented by using other modules. > > For instance when running a playbook with: > > shell: git clone https://... > > The system will warn and suggest the git module be used. > > This can be surpressed with: > > shell: git clone https:// warn=no > > If warnings are meant to be on be default in ansible.cfg. > > It's on by default but can be toggled with "command_warnings=False" in > ansible.cfg > > I'm open to feedback on this and whether it should be on by default or off > by default. > > I want to pick the right option that's good for everyone, but I also feel > there's a huge bonus to having everyone write better playbooks. > > In any case, the development branch is the right place to try it out. > > Thoughts? > > --Michael > > > > > -- 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/CA%2BnsWgwotcmiHNvchxNKPF4Pmkp%2BaMqg9jzp%2BFPAcHu3C0vMAw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
