No such guide.   Maybe it should.  I need to think about what it might say.

Ultimately it's probably best to show the hack and ask how to do it better
when you see the specific hack.

I've also been thinking a bit about a "tuning" section, as I've been seeing
a fair amount of people who aren't aware of accelerate mode or
ControlMaster/pipelining even though they are in the docs.   There are some
other tricks to put in there as well (forks, with_items for package
operations, etc).





On Tue, May 27, 2014 at 4:46 PM, Adam Morris <[email protected]> wrote:

> I have heard rumours that there is a mystic who enlightens his disciples
> with the Zen of Ansible...
>
> I have even seen some bits and pieces of his teachings along the way, but
> was wondering if there was a more definitive source somewhere.
>
> Here is some of the advice I have seen attributed to this sage:-
>
> Keep things simple.
>
> Don't think about trying to read what some default value is.   Just use
> the value that makes it through, knowing that the right value made it
> through.
>
> Once you get the bare minimum to automate application X, stop.
>
> It's not supposed to be a super-elegant software construct, or even a
> programming language.  It's a language for getting things done.
>
> And paraphrasing...
>
> If your Jinja2 templates are getting complex perhaps you are doing it
> wrong.
>
> Hacks should be shunned.
>
>
> OK I admit it was Michael DeHaan who said these things, but I was
> seriously wondering if there was a definitive guide to "The Zen of
> Ansible".
>
> Sometimes I have resorted to "hacks" when a different way might have been
> cleaner... (my hack to bring crontab entries under support of the cron
> module definitely qualifies as a hack, replacing the file might be cleaner,
> but has distinct issues as well).
>
> Does such a document exist?  If it doesn't should it?
>
> Adam
>
>  --
> 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/15e32f3a-3032-4c0c-8ceb-80d84f7aa2b4%40googlegroups.com<https://groups.google.com/d/msgid/ansible-project/15e32f3a-3032-4c0c-8ceb-80d84f7aa2b4%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%2BnsWgxUUos%2BA6Ftoo4FQckadZNT38N8o%3DnxAaP3PtDqbS8GuQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to