On Wednesday, July 2, 2014 5:18:05 PM UTC-7, Michael DeHaan wrote:
>
> Yes, they did, and this was unfortunate.
>
> This was a fix to prevent nodes from returning facts that contain Jinja2
> expressions (which long story short could result in some hijinx), and
> because the filter choices are made in the template here, we had to remove
> the feature for allowing the block delimiters like {{ and {% to be changed
> in order to reliably filter these out.
>
> Now, I think what we should probably do (it would have to be on the devel
> branch) is make this option *ONLY* be able to set trim_blocks (and maybe
> another whitelist of certain options).
>
> Is this something you might like to take a crack at?
>
Yes: https://github.com/ansible/ansible/pull/8026
It doesn't raise an error for settings Ansible no longer supports,
primarily because I couldn't figure out the plumbing. But it is a
whitelist, and it does work, so there's that.
--
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/b68767cb-14f6-4b97-a6de-cfcaee63e430%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
