From de4d4bcc80b78b7f03f58649e10035c6f7996ad2 Mon Sep 17 00:00:00 2001 From: Anuvrat Parashar Date: Sat, 27 Jun 2015 12:30:45 +0530 Subject: [PATCH 1/4] grammatical rearrangements. --- docsite/rst/playbooks_vault.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docsite/rst/playbooks_vault.rst b/docsite/rst/playbooks_vault.rst index 25dae8f5f3b..241e418d311 100644 --- a/docsite/rst/playbooks_vault.rst +++ b/docsite/rst/playbooks_vault.rst @@ -14,7 +14,7 @@ What Can Be Encrypted With Vault The vault feature can encrypt any structured data file used by Ansible. This can include "group_vars/" or "host_vars/" inventory variables, variables loaded by "include_vars" or "vars_files", or variable files passed on the ansible-playbook command line with "-e @file.yml" or "-e @file.json". Role variables and defaults are also included! -Because Ansible tasks, handlers, and so on are also data, these can also be encrypted with vault. If you'd like to not betray what variables you are even using, you can go as far to keep an individual task file entirely encrypted. However, that might be a little much and could annoy your coworkers :) +Because Ansible tasks, handlers, and so on are also data, these can also be encrypted with vault. If you'd not like to betray even the variables you are using, you can go as far as keeping individual task files entirely encrypted. However, that might be a little too much and could annoy your coworkers :) .. _creating_files: From c17d8b943900ec2b58e11206ba997d6400140c19 Mon Sep 17 00:00:00 2001 From: Anuvrat Parashar Date: Sat, 27 Jun 2015 12:34:12 +0530 Subject: [PATCH 2/4] [grammar nazi] rearrangment. --- docsite/rst/playbooks_vault.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docsite/rst/playbooks_vault.rst b/docsite/rst/playbooks_vault.rst index 241e418d311..745b6f21c22 100644 --- a/docsite/rst/playbooks_vault.rst +++ b/docsite/rst/playbooks_vault.rst @@ -14,7 +14,7 @@ What Can Be Encrypted With Vault The vault feature can encrypt any structured data file used by Ansible. This can include "group_vars/" or "host_vars/" inventory variables, variables loaded by "include_vars" or "vars_files", or variable files passed on the ansible-playbook command line with "-e @file.yml" or "-e @file.json". Role variables and defaults are also included! -Because Ansible tasks, handlers, and so on are also data, these can also be encrypted with vault. If you'd not like to betray even the variables you are using, you can go as far as keeping individual task files entirely encrypted. However, that might be a little too much and could annoy your coworkers :) +Because Ansible tasks, handlers, and so on are also data, these too can be encrypted with vault. If you'd not like to betray even the variables you are using, you can go as far as keeping individual task files entirely encrypted. However, that might be a little too much and could annoy your coworkers :) .. _creating_files: From 0070e17750fa97bf69970c7be60658c698cc29d3 Mon Sep 17 00:00:00 2001 From: Anuvrat Parashar Date: Wed, 1 Jul 2015 09:29:44 +0530 Subject: [PATCH 3/4] full rewrite of the paragraph. following @abadger's suggestion[1] in the comments [1] https://github.com/ansible/ansible/pull/11410#issuecomment-116049590 --- docsite/rst/playbooks_vault.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docsite/rst/playbooks_vault.rst b/docsite/rst/playbooks_vault.rst index 745b6f21c22..3fbcd87369d 100644 --- a/docsite/rst/playbooks_vault.rst +++ b/docsite/rst/playbooks_vault.rst @@ -14,7 +14,7 @@ What Can Be Encrypted With Vault The vault feature can encrypt any structured data file used by Ansible. This can include "group_vars/" or "host_vars/" inventory variables, variables loaded by "include_vars" or "vars_files", or variable files passed on the ansible-playbook command line with "-e @file.yml" or "-e @file.json". Role variables and defaults are also included! -Because Ansible tasks, handlers, and so on are also data, these too can be encrypted with vault. If you'd not like to betray even the variables you are using, you can go as far as keeping individual task files entirely encrypted. However, that might be a little too much and could annoy your coworkers :) +Ansible tasks, handlers, and so on are also data so these can be encrypted with vault as well. If you don't want to even reveal the variables you are using you can go as far as keeping individual task files entirely encrypted. However, that might be a little too much and could annoy your coworkers :) .. _creating_files: From f9bf6ce4d0bd90cc08eb296aa04c1474b1870a41 Mon Sep 17 00:00:00 2001 From: Anuvrat Parashar Date: Wed, 1 Jul 2015 09:54:02 +0530 Subject: [PATCH 4/4] makes it more concise. @msabramos's suggestions[1] incorporated. [1] https://github.com/ansible/ansible/pull/11410#issuecomment-116319780 --- docsite/rst/playbooks_vault.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docsite/rst/playbooks_vault.rst b/docsite/rst/playbooks_vault.rst index 3fbcd87369d..5cb1eb90c9c 100644 --- a/docsite/rst/playbooks_vault.rst +++ b/docsite/rst/playbooks_vault.rst @@ -14,7 +14,7 @@ What Can Be Encrypted With Vault The vault feature can encrypt any structured data file used by Ansible. This can include "group_vars/" or "host_vars/" inventory variables, variables loaded by "include_vars" or "vars_files", or variable files passed on the ansible-playbook command line with "-e @file.yml" or "-e @file.json". Role variables and defaults are also included! -Ansible tasks, handlers, and so on are also data so these can be encrypted with vault as well. If you don't want to even reveal the variables you are using you can go as far as keeping individual task files entirely encrypted. However, that might be a little too much and could annoy your coworkers :) +Ansible tasks, handlers, and so on are also data so these can be encrypted with vault as well. To hide the names of variables that you're using, you can encrypt the task files in their entirety. However, that might be a little too much and could annoy your coworkers :) .. _creating_files: