The PR will break some current and future things and needs some revision -
open to exploring it, but it may need to wait until after 1.7
I'm curious in particular why you needed to override the template codes
though, was the configuration file already in Jinja2 syntax, etc?
What I'm possibly suggesting for you right now would be to use the raw
keyword in Ansible where "{{" needed to be preserved:
http://jinja.pocoo.org/docs/templates/#escaping
Curious on details if that appears to not work for you.
(We have definitely stopped using coderwall, since it's difficult to
comment on tips that have been superceeded, and other things -- in most
cases, we prefer getting tips and tricks into the docs)
On Fri, Aug 1, 2014 at 9:29 AM, Sarah Zelechoski <[email protected]>
wrote:
> I had been using custom variable enclosures with #jinja2 templates, but
> since updating from ansible 1.5.4-> 1.6.x I've had these break.
>
> I was using this feature for cases in which I wanted to provision a VM
> using an ansible role that deploys a collection of support playbooks. The
> idea being that these playbooks could then be used locally (connection:
> local) by support technicians on the endpoint. These playbooks were for
> everyday tasks such as changing the hostname, running a support collect,
> etc.
>
> Here I describe an example that used to work:
> https://coderwall.com/p/kci7ca
>
> Doing some digging, I've found that the feature was broken purposefully
> because of a security concern. There seems to be a PR (
> https://github.com/ansible/ansible/pull/8040) for a fix, but there has
> been no movement on it.
>
> @laserllama on twitter mentioned that there may be a better way to do such
> things. What's the current news on this feature? What kind of workarounds
> are people using?
>
> Have a great Friday,
> Sarah
>
> --
> 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/feb5c8dc-5530-430e-98aa-5faf26c7d3fd%40googlegroups.com
> <https://groups.google.com/d/msgid/ansible-project/feb5c8dc-5530-430e-98aa-5faf26c7d3fd%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%2BnsWgyLA3LMCDMqsWkUhPsR1dLMX%2BfSAxo%3Dn_kjGyje_6-hiQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
