Skip to main content

Ansible comment all existing lines and add new lines

Backing up every configuration before any change is a good idea. 

With the Git tool, every revision or change can be keep track and changes can be reversed.

However, not everything is in Git. For example, in Linux configuration on /etc configuration or other important location or files is not under Git.

To keep track of the changes, old school method can still be applied.

Making another copy of the file, or just simply commenting every line and adding changes or new configuration after commenting the existing lines or configuration; are forms of backup.

Existing configuration can still be seen, and can put back if there's a need to reverse the configuration.

In an environment where there is hundred or more virtualized machines, Ansible is a way to go. 

Ansible can do the task to comment all the existing lines and apply new configurations.

Ansible script below, are references from multiple sources found on the web to create this Ansible script below.

Here's the Ansible, save it as a YAML file. Apply it to a Test Server or  VM before deploying to production to make sure the output is the expected result.

---

- hosts: Server-Test-Machine

  tasks:

    - name: Add # to the start of every line in the file, existing entries will be commented

      ansible.builtin.replace:

        path: /etc/resolv.conf

        regexp: '^(.*)$'

        replace: '#\1'

  vars:

    lines_to_add:

      - "First Test line to add."

      - "Second Test line to add."

      - "nameserver 8.8.8.8"

  tasks:

    - name: Add above multiple lines to a file using lineinfile, or add the new entries

      ansible.builtin.lineinfile:

        path: /etc/resolv.conf

        line: "{{ item }}"

        state: present

      loop: "{{ lines_to_add }}"


That's it, it will simplify the task of backing up existing configuration and also making or applying new changes to the configuration. Modify it for any use cases that the Ansible script can be applied.


Enjoy Scripting...


Stay safe! and Keep things up! 

Do ASAP, Always Say A Prayer...

Practice O.T.G. = Obedience To God

Make time for Prayer and Meditation.

================================

Free Android Apps:

Click  links below to find out more:

Free Android Apps:

Click  links below to find out more:

Excel Keyboard guide:

https://play.google.com/store/apps/details?id=chrisjoms.myexcelapplicationguide

Heaven's Dew Fall  Prayer app for Android :

https://play.google.com/store/apps/details?id=soulrefresh.beautiful.prayer

Catholic Rosary Guide  for Android:

Pray the Rosary every day, countless blessings will be showered upon your life if you recite the Rosary faithfully. 

https://play.google.com/store/apps/details?id=com.myrosaryapp

Divine Mercy Chaplet Guide (A Powerful prayer) BFF = Be Filled Faith:

https://play.google.com/store/apps/details?id=com.dmercyapp   

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

WMIC get computer name

WMIC get computer model, manufacturer, computer name and  username. WMIC is a command-line tool and that can generate information about computer model, its manufacturer, its username and other informations depending on the parameters provided. Why would you need a command line tool if there’s a GUI to check? If you have 20 or 100 computers, or even more. It’s quite a big task just checking the GUI to check the computer model and username. If you have remote computers, you need to delegate someone in the remote office or location to check. Or you can just write a batch file or script to automate the task. Here’s the code below on how get computer model, manufacturer and the username. Open an elevated command prompt and type:     wmic computersystem get "Model","Manufacturer", "Name", "UserName" Just copy and paste the code above, the word “computersystem” does not need to be change to a computer name. A...
Post a Comment
Read more

Print error 016-799 - Fuji Film Xerox

016-799 Fuji Xerox or Fuji Film print error code. That shows a description error as “Print instruction Fail detected in decomposer.” The error code and error description are alien languages for users and even system administrators who are not familiar with Fuji Xerox error code. The error code is quite simple and easy to fix, if the job print goes to the printer but print out doesn’t come out. So, basically the print job was received by the printer, but the printer just doesn’t know what type of paper or what size to use or which tray to utilize for the print out. In some instances, this is just a paper mismatch but the error description; if using Windows 10 to print does not exactly points to what is the issue. First thing to check, is the paper size selected by the user to print. Example, if the printer configuration is A3 and A4 sizes only. But then the person printing the file accidentally chooses “A4 Cover” then this error 016-799 will occur. ...
6 comments
Read more

How to check office version from command line

The are quite a few ways to check office version it can be done via registry, PowerShell or VBScript and of course, good old command line can also do it. Checking Windows office version whether it is Office 2010, Office, 2013, Office 2016 or other version is quite important to check compatibility of documents; or just a part of software inventory. For PowerShell this simple snippet can check the office version: $ol = New-Object -ComObject Excel.Application $ol . Version The command line option will tell you where’s the path located; the result will also tell whether office is 32-bit, 64-bit and of course the version of the office as well. Here’s the command that will check the office version and which program directory the file is located which will tell whether it’s 32-bit or 64-bit. Command to search for Excel.exe: DIR C:\ /s excel.exe | find   /i "Directory of"  Above command assumes that program files is on  C: drive. Sample O...
Post a Comment
Read more