Removed obsolete parts about var_pass.yml and ansible_become_password variable from the README

README.md

@@ -44,13 +44,9 @@ ansible
   |_ group_vars
   |       |
   |       |_ iRODS
-  |       |    |
-  |       |    |_ main.yml
-  |       |
-  |       |_ all
-  |           |
-  |           |_ var_pass.yml (optional)
-  |
+  |            |
+  |            |_ main.yml
+  |                             
   |_ host_vars
   |      |
   |      |_ myhost1.mydomain.tld
@@ -62,21 +58,6 @@ ansible
        |_ postgresql
 ```
 
-**OPTIONAL:** privilege escalation (sudo) sometimes relies on the "ansible_become_password" variable in group_vars/all/var_pass.yml file (it should be vaulted):
-
-```bash
-cd ansible/group_vars/all/
-ansible-vault create var_pass.yml
-```
-
-```
----
-
-ansible_become_password: your password to sudo privileges on the target machines 
-
-...
-```
-
 **N.B:** The provider / consumer installation mode is handled with the "irods_server_mode" variable in host_vars/myhost1.mydomain.tld file:
 
 ```
@@ -197,7 +178,9 @@ ssh-copy-id -i /home/user/.ssh/ansible_id_rsa.pub user@myhost2.mydomain.tld
 
 ```bash
 cd ansible
-ansible-playbook --key-file=/path/to/your/.ssh/ansible_id_rsa -i irods_hosts irods.yml ((--ask-vault-pass)) --vault-id irods@prompt
+ansible-playbook --key-file=/path/to/your/.ssh/ansible_id_rsa -i irods_hosts irods.yml --vault-id irods@prompt
 ```
 
-The ansible-playbook command will then ask you to input either one or two passwords in order to decrypt your vaulted variables.
+The ansible-playbook command will then ask you to input your password in order to decrypt your vaulted variables.
+
+**N.B:** in case you'd need a password to become another user using "sudo", just add the "-K" option to your ansible-playbook command line, and you'll be prompted for it.