thank you for the explanation

On Wednesday, January 13, 2016 at 9:38:39 AM UTC-8, tkuratomi wrote:
>
> In 1.9.4, you'll need to use 
> - { dest: "/boot/loader.conf", regexp: "^vmm_load", line: 
> vmm_load=\\\"YES\\\", state: "present", backup: "no", create: "yes" } 
>
> (three backslashes). 
>
> In 2.0 we fixed this so that \" will work correctly there. 
>
> Quoting and escaping is tricky inside of the ansible code because we 
> use yaml to parse the playbook and then jinja2 to substitute 
> variables.  We try to abstract that away but sometimes it leaks out 
> and you end up having to escape for both of the parsers.  Hopefully we 
> fixed most of those in 2.0. 
>
> -Toshio 
>
> On Tue, Jan 12, 2016 at 12:51 PM, Joel Parker <[email protected] 
> <javascript:>> wrote: 
> > Any thoughts? 
> > 
> > On Sunday, January 10, 2016 at 10:45:16 PM UTC-8, Joel Parker wrote: 
> >> 
> >> I know this has been a bug in the recent past, but I'm running into 
> this 
> >> with Ansible 1.9.4 on FreeBSD. 
> >> 
> >>  - name: update loader.conf 
> >>     lineinfile: dest={{ item.dest }} regexp={{ item.regexp }} line={{ 
> >> item.line}} state={{ item.state }} backup={{ item.backup }} create={{ 
> >> item.create }} 
> >>     with_items: 
> >>       - { dest: "/boot/loader.conf", regexp: "^vmm_load", line: 
> >> "vmm_load=\"YES\"", state: "present", backup: "no", create: "yes" } 
> >> 
> >> 
> >> Obviously I'm wanting the result to be: 
> >> vmm_load="YES" 
> >> 
> >> However the actual result is: 
> >> vmm_load=YES 
> >> 
> >> 
> >> I do see that the following *does* work as expected (note removed 
> quotes): 
> >>  - name: update loader.conf 
> >>     lineinfile: dest={{ item.dest }} regexp={{ item.regexp }} line={{ 
> >> item.line}} state={{ item.state }} backup={{ item.backup }} create={{ 
> >> item.create }} 
> >>     with_items: 
> >>       - { dest: "/boot/loader.conf", regexp: "^vmm_load", line: 
> >> vmm_load=\"YES\", state: "present", backup: "no", create: "yes" } 
> >> 
> >> 
> >> Am I incorrectly placing double quotes around everything in my dict, or 
> is 
> >> ansible failing to handle yaml like it should? 
> > 
> > -- 
> > 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] <javascript:>. 
> > To post to this group, send email to [email protected] 
> <javascript:>. 
> > To view this discussion on the web visit 
> > 
> https://groups.google.com/d/msgid/ansible-project/83d4be58-6cca-44b1-9bd1-5295920408d9%40googlegroups.com.
>  
>
> > 
> > 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/de5c1ab9-f8fc-4f36-80d3-2c7b5fa7c952%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to