Ansible Lineinfile is a module of Ansible that is utilized to adjust the specific line in a document. It is helpful to add another line, adjust a line, supplant a line, and eliminate a current line in a record if it tracks down a particular text. We can utilize a customary articulation to apply search conditions while working with the Lineinfile module. It has cool choices that make our occupation more straightforward. For instance, assuming we need to embed a line in a record on various hosts and we are don't know that document is available on the hosts or not, we can utilize 'make' choices and make it 'yes' to stay away from mistakes that we will experience on the off chance that the document doesn't exist on the objective.

Fundamentally, the Lineinfile module takes the document name utilizing the 'way' boundary as it is the necessary choice for this module and rolls out the improvements in a record according to other given boundaries like what activity we need to perform on that document. The module can take a reinforcement before rolling out any improvements assuming we have indicated the 'reinforcement' choice to yes as it is a discretionary boundary, nonetheless, it is prescribed to take a reinforcement of the record utilizing 'reinforcement' so we can get the first document back on the off chance that the progressions made to the record are wrong.

We should find out with regards to different tasks we can perform utilizing the 'Lineinfile' module and how:

We can insert a line in a file using the ‘line in file’ module. By default, It adds the line at the end of the file if does not exist. Here is a playbook for the same:

- name: "Insert a line in a file and if create the file if does not exist"

ansible test_group -m shell -a “ls /root/testing”

Explanation: In the above example, we got an error because the file does not exist at the destination and we have not specified the ‘create’ option. Let’s add the ‘create’ option and make it to yes.

Explanation: In the above example, we have added the ‘create’ option and re-ran the playbook and it ran without any error. Below command is used to verify that there was no file present named ‘test_file2’ before running the playbook:

ansible test_group -m shell -a "ls /root/testing"

As referenced over, the 'lineinfile' module just adds the line toward the finish of the document of course, be that as it may, we can add line later and before a particular line utilizing the 'insertafter' and 'insertbefore' choices separately. Here is the preview of the record test document that we will alter.

Below is the playbook to insert line after a specific line: –

- name: "Check existence of a String in a file and add the line after it"

ansible test_group -m shell -a "cat /root/testing"

Explanation: In the above model, we have added 'ansible_client' line after the line that matches 'ServerName'. Similarly, we can involve the 'insertbefore' choice instead of the 'insertafter' choice to add the line before the particular line on the off chance that it tracks down the match. Model will be shown when we alter the line in the record. 

We can supplant a line utilizing the 'lineinfile' module anyway it will possibly supplant one line in a record in the event that there are numerous lines match the predetermined customary articulation. 'lineinfile' module utilizes the 'regexp' choice to match the rules. It replaces the last line that matches the rules of course. We can handle it utilizing the 'firstmatch' choice to supplant the principal line that matches the rules. Ansible has 'supplant' module to supplant every one of the events in the record. We will utilize a similar test record that is referenced above to see it in real life and assuming you have recalled that we have added 'ansible_client' after the line that has 'ServerName' text in it.

Here is the playbook to supplant the line in a record:

- name: "Check existence of a String in a file and replace if it finds the match"

Explanation: In the above example, we have replaced the line that matches ‘ansible_client’ text in it with ‘ansible_master’. We can see the difference if we compare the above snapshot with the last snapshot. In the last snapshot, the third line was ‘ansible_client’ that is replaced with ‘ansible_master’ as we see in the above snapshot.

Below command is used to search for ‘ansible_master’ in the ‘test_file’:

ansibletest_group -m shell -a "grep -in ansible_master /root/test_file"

3. Removing all Lines from a File that Matches the Criteria

We can search for the lines that match specific criteria using the ‘regexp’ option and remove those lines by changing the ‘state’ option to absent. Here is the playbook for the same:

In this blog post, We will discuss Ansible lineinfile.

Explaining of Ansible  lineinfile

Explanation: In the above example, we have added the ‘create’ option and re-ran the playbook and it ran without any error. The below command is used to verify that there was no file present named ‘test_file2’ before running the playbook:

As referenced over, the 'line in file' module just adds the line toward the finish of the document, of course, be that as it may, we can add a line later and before a particular line utilizing the 'insert after' and 'insert before' choices separately. Here is the preview of the record test document that we will alter.

Explanation: In the above model, we have added the 'ansible_client' line after the line that matches 'ServerName'. Similarly, we can involve the 'insert before' choice instead of the 'insert after' choice to add the line before the particular line on the off chance that it tracks down the match. The model will be shown when we alter the line in the record. 

We can supplant a line utilizing the 'line in file' module anyway it will possibly supplant one line in a record if there are numerous lines that match the predetermined customary articulation. 'line in file' module utilizes the 'regexp' choice to match the rules. It replaces the last line that matches the rules of course. We can handle it utilizing the 'first match' choice to supplant the principal line that matches the rules. Ansible has a 'supplant' module to supplant every one of the events in the record. We will utilize a similar test record that is referenced above to see it in real life and assume you have recalled that we have added 'ansible_client' after the line that has 'ServerName' text in it.

ansible lineinfile

Trending Blogposts on ansible lineinfile

Explaining of Ansible lineinfile

Explaining of Ansible lineinfile

Popular Discussions on ansible lineinfile

PRODUCTS

QUICK LINKS

LEGAL

ansible lineinfile

Trending Blogposts on ansible lineinfile

Explaining of Ansible lineinfile

Explaining of Ansible lineinfile

Popular Discussions on ansible lineinfile