DevOps Hunter Security Automation

In this post, we will discuss the possible options for ansible variables precedence, Experiment with few host_vars, group_vars, and their variable precedence. You can specify the variables along with the host inside your inventory itself.  Ansible host_vars and group_vars and usage options The command-line variable will be the highest priority. To test the variable precedence, top priority extra vars ansible -i "node1," all \ -e "var1=VybhavaTechnologies" \ -m debug -a 'msg={{ var1 }}' Here -i use the target host and the group name to define an extra variable that will have the highest priority. Using debug module we can get the var1 value using jinja format to print. ansible extra variables highest precedence  Let's see the following example:   Create the inventory.yml file in "dev" directory. inventory.yml all: children: common: children: webserver: hosts: node[1:2]: ...

Overview of Ansible PLAYBOOK  An Ansible playbook is a single YAML file that contains multiple plays.  Each Play will be defined with a set of activities that are treated as tasks,  and these tasks can be executed at the remote host that is the Ansible client. The task can be a single action that can be one of:   Execute a command    Run a script    install patch or package   Reboot VM/box    Restart services Simple ansible play can be  check the timestamp reboot server wait for connect back check the uptime  check timestamp  Complex ansible play Take a backup of files on 20 DB VMs Deploy application on 100 App boxes 100 servers patch apply 100 VM reboot after patch  Mail and slack notifications on patch process  Ansible ad-hoc command When you plan to write a playbook first you need to test the ad-hoc commands as trial and error will gives more confidence to run in a play # Ansible ad-...