Merge

01-Introduction/02-Installation.md

@@ -33,7 +33,7 @@ have python2 or python3 installed on them.
   $ pip3 install ansible --user
 ```
 
-**Script to add user, password and enable password authentication**
+**Script (for remote nodes) to add user, password and enable password authentication**
 ```
 #!/bin/bash
 $ sudo useradd -d /home/ansible -s /bin/bash -m ansible

01-Introduction/03-Ansible_config_file.md

@@ -12,7 +12,12 @@
 - But we can define ansible configuration file in different location
 and for this there is a priority for this files.
 - You can generate ansible.cfg by running the command
-    $ ansible-config init --disabled > ansible.cfg
+
+  **ansible-config init --disabled > ansible.cfg**
+
+- Also you can now have a more complete file by including existing plugins:
+
+    **ansible-config init --disabled -t all > ansible.cfg**
 
 **Locations with priority(starting from top to bottom):** 
 - ANSIBLE_CONFIG environment variable  

01-Introduction/terraform files/null-resource.tf

@@ -7,7 +7,7 @@ resource "null_resource" "vscode-config" {
     host        = aws_instance.ubuntu.public_ip
     user        = "ubuntu"
     password    = ""
-    private_key = file("~/Downloads/ansible-key.pem")
+    private_key = file("~/Downloads/AutomationKey.pem")
   }
 
   provisioner "file" {

01-Introduction/terraform files/variables.tf

@@ -10,10 +10,10 @@ variable "my_instance_type" {
 
 variable "my_key" {
   type    = string
-  default = "ansible-key"
+  default = "AutomationKey"
 }
 
 variable "os" {
   type    = string
   #default = "linux"
-}
+}

04-Ansible modules/Type_module.md

@@ -34,7 +34,7 @@ a) From ansible control node to remote node \
   **$ ansible group1 -m copy -a "src=/source/file/path dest=/dest/location"** \
   **$ ansible group1 -m copy -a "src=/etc/hosts dest=/home/ansible"**
 
- b) From one location in remote node to another location in remote node \
+ b) From one location in remote node to another location in (same) remote node \
   **$ ansible db -m copy -a “src=/source/file/path dest=/dest/location remote_src=yes"**
 
   **$ ansible group1 -m copy -a "src=/etc/hosts dest=/home/ansible remote_src=yes"**
@@ -67,26 +67,35 @@ a) From ansible control node to remote node \
 
   **$ ansible all -m service -a "name=nginx state=stopped" --become  -K**
 
-## **8. User Module**
+## **8. User Module (Ansible3 00:56:18)**
  - Used to create user accounts.
  - Create a password encryption
  - Generate the password from your local environment
 
  **$ openssl passwd -crypt <desired_password>**
+
+ **On macOS, the openssl passwd -crypt command is not available by default in OpenSSL. The -crypt option is more commonly found on Linux systems.
+However, you can achieve similar functionality using Python or Perl to generate a password hash with the crypt function. Here's an example using Python:*
 
+**python -c 'import crypt,getpass; print(crypt.crypt(getpass.getpass(), crypt.mksalt(crypt.METHOD_CRYPT)))'**
+
+**The above Python command will prompt you to enter the desired password, and it will output the hashed password* using the crypt method.
+
+ **Then to create the user and pass the decrypted password, run the following:*
+
  **$ ansible db -m user -a "name=Peter password=wiyiMQbLhCRUY shell=/bin/bash" -b**
 
 ## **9. Setup module**
 - This is a default module and is used to gather facts about the hosts.
 - The setup module returns detailed information about the remote systems managed by Ansible, also known as system facts.
 - To obtain the system facts for group1, run:
 
-  **$ ansible group1 -m setup**
+  **$ ansible groupName -m setup**
 
 - This will print a large amount of JSON data containing details about the remote server environment.
 - To print only the most relevant information, include the "gather_subset=min" argument as follows:
 
-  **$ ansible group1 -m setup -a "gather_subset=min"**
+  **$ ansible groupName -m setup -a "gather_subset=min"**
 
 - To print only specific items of the JSON, you can use the filter argument. This will accept a wildcard pattern used to match strings. For example, to obtain information about both the ipv4 and ipv6 network interfaces, you can use *ipv* as filter:
 

05-Playbooks/ReadMe.md

@@ -66,7 +66,8 @@
 ```
 ---
  - name: sonarqube playbook
-   hosts: sonarqube become: yes
+   hosts: sonarqube
+   become: yes
    tasks:
  - name: install java
    yum:
@@ -87,4 +88,4 @@
  - name: start sonarqube
    shell: sh /opt/sonarqube/sonarqube-7.8/bin/linux-x86-64/sonar.sh start become: yes
    become_user: sonar
-```
+```