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. For more options, visit https://groups.google.com/d/optout.
