How to use escape characters in lineinfile ansible












0















I am writing the ansible play for adding the users.



So far I got this.



- name: Add user to sudoers
hosts: all_hosts
su: yes
su_user: root
tasks:
- lineinfile: line='worker_temp ALL=(ALL) NOPASSWD: /bin/sh' dest='/etc/sudoers'


I am able to add the user which is another task.
I am trying to add the same user in the sudoers file.
It fails



ERROR! Syntax Error while loading YAML.
mapping values are not allowed here

at - lineinfile: line="worker_temp ALL=(ALL) NOPASSWD: /bin/sh" dest="/etc/sudoers"
^ here


I tried by adding escaping quotes, but then it appendsthe folloing line in sudoers file



worker_temp ALL=(ALL) NOPASSWD':' /bin/sh


this line has '' unwanted around :



How can I get only



worker_temp ALL=(ALL) NOPASSWD: /bin/sh


Thanks.










share|improve this question


















  • 1





    I don't understand why you are opposed to the line='' syntax, but either way, if you switch to the formal YAML map syntax this entire discussion evaporates

    – Matthew L Daniel
    Nov 13 '18 at 3:21
















0















I am writing the ansible play for adding the users.



So far I got this.



- name: Add user to sudoers
hosts: all_hosts
su: yes
su_user: root
tasks:
- lineinfile: line='worker_temp ALL=(ALL) NOPASSWD: /bin/sh' dest='/etc/sudoers'


I am able to add the user which is another task.
I am trying to add the same user in the sudoers file.
It fails



ERROR! Syntax Error while loading YAML.
mapping values are not allowed here

at - lineinfile: line="worker_temp ALL=(ALL) NOPASSWD: /bin/sh" dest="/etc/sudoers"
^ here


I tried by adding escaping quotes, but then it appendsthe folloing line in sudoers file



worker_temp ALL=(ALL) NOPASSWD':' /bin/sh


this line has '' unwanted around :



How can I get only



worker_temp ALL=(ALL) NOPASSWD: /bin/sh


Thanks.










share|improve this question


















  • 1





    I don't understand why you are opposed to the line='' syntax, but either way, if you switch to the formal YAML map syntax this entire discussion evaporates

    – Matthew L Daniel
    Nov 13 '18 at 3:21














0












0








0








I am writing the ansible play for adding the users.



So far I got this.



- name: Add user to sudoers
hosts: all_hosts
su: yes
su_user: root
tasks:
- lineinfile: line='worker_temp ALL=(ALL) NOPASSWD: /bin/sh' dest='/etc/sudoers'


I am able to add the user which is another task.
I am trying to add the same user in the sudoers file.
It fails



ERROR! Syntax Error while loading YAML.
mapping values are not allowed here

at - lineinfile: line="worker_temp ALL=(ALL) NOPASSWD: /bin/sh" dest="/etc/sudoers"
^ here


I tried by adding escaping quotes, but then it appendsthe folloing line in sudoers file



worker_temp ALL=(ALL) NOPASSWD':' /bin/sh


this line has '' unwanted around :



How can I get only



worker_temp ALL=(ALL) NOPASSWD: /bin/sh


Thanks.










share|improve this question














I am writing the ansible play for adding the users.



So far I got this.



- name: Add user to sudoers
hosts: all_hosts
su: yes
su_user: root
tasks:
- lineinfile: line='worker_temp ALL=(ALL) NOPASSWD: /bin/sh' dest='/etc/sudoers'


I am able to add the user which is another task.
I am trying to add the same user in the sudoers file.
It fails



ERROR! Syntax Error while loading YAML.
mapping values are not allowed here

at - lineinfile: line="worker_temp ALL=(ALL) NOPASSWD: /bin/sh" dest="/etc/sudoers"
^ here


I tried by adding escaping quotes, but then it appendsthe folloing line in sudoers file



worker_temp ALL=(ALL) NOPASSWD':' /bin/sh


this line has '' unwanted around :



How can I get only



worker_temp ALL=(ALL) NOPASSWD: /bin/sh


Thanks.







ansible ansible-2.x






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 13 '18 at 0:18









User007User007

1,66042650




1,66042650








  • 1





    I don't understand why you are opposed to the line='' syntax, but either way, if you switch to the formal YAML map syntax this entire discussion evaporates

    – Matthew L Daniel
    Nov 13 '18 at 3:21














  • 1





    I don't understand why you are opposed to the line='' syntax, but either way, if you switch to the formal YAML map syntax this entire discussion evaporates

    – Matthew L Daniel
    Nov 13 '18 at 3:21








1




1





I don't understand why you are opposed to the line='' syntax, but either way, if you switch to the formal YAML map syntax this entire discussion evaporates

– Matthew L Daniel
Nov 13 '18 at 3:21





I don't understand why you are opposed to the line='' syntax, but either way, if you switch to the formal YAML map syntax this entire discussion evaporates

– Matthew L Daniel
Nov 13 '18 at 3:21












1 Answer
1






active

oldest

votes


















1














You can only escape quotes if you actually quote a scalar, and in your example the value to the key linenfile is not a quoted scalar as this is the value:



line='worker_temp ALL=(ALL) NOPASSWD: /bin/sh' dest='/etc/sudoers'


(although there are quotes in the scalar, a quoted scalar needs to start (and end) with a single or double quote).



Just putting double quotes around that will prevent your parser from mis interpreting the second : on that line as a value indicator as well as first:



- lineinfile: "line='worker_temp ALL=(ALL) NOPASSWD: /bin/sh' dest='/etc/sudoers'"





share|improve this answer























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53272007%2fhow-to-use-escape-characters-in-lineinfile-ansible%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1














    You can only escape quotes if you actually quote a scalar, and in your example the value to the key linenfile is not a quoted scalar as this is the value:



    line='worker_temp ALL=(ALL) NOPASSWD: /bin/sh' dest='/etc/sudoers'


    (although there are quotes in the scalar, a quoted scalar needs to start (and end) with a single or double quote).



    Just putting double quotes around that will prevent your parser from mis interpreting the second : on that line as a value indicator as well as first:



    - lineinfile: "line='worker_temp ALL=(ALL) NOPASSWD: /bin/sh' dest='/etc/sudoers'"





    share|improve this answer




























      1














      You can only escape quotes if you actually quote a scalar, and in your example the value to the key linenfile is not a quoted scalar as this is the value:



      line='worker_temp ALL=(ALL) NOPASSWD: /bin/sh' dest='/etc/sudoers'


      (although there are quotes in the scalar, a quoted scalar needs to start (and end) with a single or double quote).



      Just putting double quotes around that will prevent your parser from mis interpreting the second : on that line as a value indicator as well as first:



      - lineinfile: "line='worker_temp ALL=(ALL) NOPASSWD: /bin/sh' dest='/etc/sudoers'"





      share|improve this answer


























        1












        1








        1







        You can only escape quotes if you actually quote a scalar, and in your example the value to the key linenfile is not a quoted scalar as this is the value:



        line='worker_temp ALL=(ALL) NOPASSWD: /bin/sh' dest='/etc/sudoers'


        (although there are quotes in the scalar, a quoted scalar needs to start (and end) with a single or double quote).



        Just putting double quotes around that will prevent your parser from mis interpreting the second : on that line as a value indicator as well as first:



        - lineinfile: "line='worker_temp ALL=(ALL) NOPASSWD: /bin/sh' dest='/etc/sudoers'"





        share|improve this answer













        You can only escape quotes if you actually quote a scalar, and in your example the value to the key linenfile is not a quoted scalar as this is the value:



        line='worker_temp ALL=(ALL) NOPASSWD: /bin/sh' dest='/etc/sudoers'


        (although there are quotes in the scalar, a quoted scalar needs to start (and end) with a single or double quote).



        Just putting double quotes around that will prevent your parser from mis interpreting the second : on that line as a value indicator as well as first:



        - lineinfile: "line='worker_temp ALL=(ALL) NOPASSWD: /bin/sh' dest='/etc/sudoers'"






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 13 '18 at 6:15









        AnthonAnthon

        29k1693145




        29k1693145






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53272007%2fhow-to-use-escape-characters-in-lineinfile-ansible%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Florida Star v. B. J. F.

            Danny Elfman

            Lugert, Oklahoma