Super easy to see this discussion bikeshed. Our policy here is to show examples and let people learn by example, without having to teach YAML.
You can use YAML and not really know all of YAML -- and that's awesome. For instance, we shy away from Anchors. I think that's enough on this topic and would wish people stay away from declaring what a "Best Practice" is. Jeff's article seems to scare me away from Ansible by making it seem there are too many rules. This is why I strongly believe in examples, and just showing what it is - exactly the way you learn to speak. You can skip what a dangling participle is, etc. On Thu, Aug 28, 2014 at 4:47 PM, Jeff Geerling <[email protected]> wrote: > I've posted the blog post: YAML best practices for Ansible playbooks - > tasks > <https://servercheck.in/blog/yaml-best-practices-ansible-playbooks-tasks> > > Only proofread once, so please let me know if you find any points of > contention or outright lies! > > -Jeff > > > > On Thursday, August 28, 2014 12:20:22 PM UTC-5, Patrick Heeney wrote: > >> I agree. I should say I have never learned full YAML and how that relates >> to ansible way of setting up the arguments. Everything I have picked up was >> from different playbooks and examples from around the web. That's why it >> would be great to have a generic use case document that ansible could point >> to for conventions and why it is good to do it that way. I imagine a blog >> post would suffice so I am looking forward to Jeff's post. >> >> Hopefully I can re-work all my playbooks soon. >> >> >> On Thu, Aug 28, 2014 at 10:14 AM, Michael Peters <[email protected]> >> wrote: >> >>> On Thu, Aug 28, 2014 at 12:34 PM, Patrick Heeney >>> <[email protected]> wrote: >>> >>> > Even with the widest screens available it is very difficult to read >>> > everything on one line. For version control as mentioned it is also a >>> lot >>> > easier to break it up. >>> > >>> > Take for example this playbook of mine: >>> > https://github.com/protobox/protobox/blob/master/lib/ >>> ansible/applications/wordpress/tasks/application.yml >>> > >>> > It would be difficult to read a lot of those on a single line. >>> >>> These are all arguments for using full YAML instead of the k=v style. >>> Not only do you get the benefits of multiple lines, but you also >>> preserve the type of the arguments whereas in the k=v style everything >>> is a string. >>> >>> -- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "Ansible Project" group. >>> To unsubscribe from this topic, visit https://groups.google.com/d/ >>> topic/ansible-project/GfJBkzuTTNM/unsubscribe. >>> To unsubscribe from this group and all its topics, 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/CAJQqANcV-w0Sp%2BfgoDawZ0zxR% >>> 2BYefefb0WHqRCx3Rg5_PFLBqw%40mail.gmail.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- > 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/b7041511-68a4-4132-b771-3347b2941c37%40googlegroups.com > <https://groups.google.com/d/msgid/ansible-project/b7041511-68a4-4132-b771-3347b2941c37%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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%2BnsWgxc6nnnXv-315foE78c5dmMezGbXmaK5VT%3Dy%3DPGnMw_BQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
