On Monday, August 25, 2014 3:25:04 PM UTC-5, Michael DeHaan wrote: > > Yep, style is a team thing. > > Part of this discussion was because Jeff is writing a book, I would prefer > if we didn't advocate that simple key=value on one line was a bad practice > in a book when it conflicts with the core docs, or that alternatively we > should encourage > structured args versus splitting on a line, since there's going to a point > where that's needed. >
Exactly why I'm asking here :) I want to present a style that I use and like, but make sure to not say "this is the Ansible way", but rather, "here are the common ways tasks are written... I prefer *this* style (whatever it turns out to be... I'm still not completely sold on any one way as a general rule) for reasons X, Y, and Z, but if you find that one of these other methods works better for you or your team, please use it. The important thing is to use a consistent style that helps you be productive and write effective playbooks... Something along those lines, but basically, since there is no official style guide for Ansible (just examples in docs and the examples repos), and since I see about a hundred different styles in the wild, I want to be comprehensive but not lead people astray. -- 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/361422a8-2013-4ec6-810e-3bfb952a42df%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
