On 2 February 2015 at 12:19, Giovanni Tirloni <[email protected]> wrote:
As an Ansible newbie, I have struggled with understanding where it's > Ansible or Jinja2 doing the parsing. So I can surely related to that. On > the other hand, Ansible tries to be simple and the looping constructs, > IMHO, are easy to work with and have a concise syntax. > Hi Giovanni, My thinking is similar. Ansible playbooks are parsed in a strange way. Some parts of it are plain YAML, whereas other parts are run through the Jinja2 templating engine. This is confusing. I was reading Salt documentation, and saw that Salt's state files are just plain YAML, but the entire YAML file is passed through Jinja2, so that any loops and other variable things are done by Jinja2, and this is conceptually neater than Ansible's current mix of Jinja2 and Ansible's own declarative language. -- 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/CANbPJF%3Dkj8fBVnwp4QxnJpJQAV5VFaQ%2BBfj9Csc8T9Yo6r6s8w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
