Ansible/Variables and Vaults - Revision history

Admin at 04:10, 16 January 2019

2019-01-16T04:10:46Z

← Older revision		Revision as of 04:10, 16 January 2019
Line 1:		Line 1:
	~~{{Main\|Ansible/Variables}}~~

	{{Main\|Ansible/Vaults}}		{{Main\|Ansible/Vaults}}

	This article covers recommendations and best practices for storing variables ~~([[Ansible/Variables]])~~ in your vault ([[Ansible/Vaults]]) while still making it possible to search variable names.		This article covers recommendations and best practices for storing variables in your vault ([[Ansible/Vaults]]) while still making it possible to search variable names.

	Ansible documentation: https://docs.ansible.com/ansible/latest/user_guide/playbooks_best_practices.html		Ansible documentation: https://docs.ansible.com/ansible/latest/user_guide/playbooks_best_practices.html

Admin: /* Flags */

2018-11-15T05:17:31Z

Flags

← Older revision		Revision as of 05:17, 15 November 2018
Line 78:		Line 78:

	==Flags==		==Flags==

			{{AnsibleFlag}}

Admin: /* After */

2018-11-15T05:09:01Z

After

← Older revision		Revision as of 05:09, 15 November 2018
Line 74:		Line 74:
	vault_database_password : strongPassword		vault_database_password : strongPassword
	vault_slack_api_key : a1a2a3a4a5a6a7		vault_slack_api_key : a1a2a3a4a5a6a7
	vault_github_api_key : b1b2b3b4b5b6b7~~</pre>~~		vault_github_api_key : b1b2b3b4b5b6b7
	</pre>		</pre>

	==Flags==		==Flags==

Admin: /* Example */

2018-11-15T05:07:00Z

Example

@@ Line 32: / Line 32: @@
 </pre>
-Now suppose we were including the full <code>vars</code> file with sensitive variables and all. It might look like this:
+Now suppose we were including the full <code>vars</code> file with sensitive variables and all.
 <pre>
@@ Line 38: / Line 44: @@
 port : 1234
 database_username : root
 database_password : strongPassword
 slack_api_key : a1a2a3a4a5a6a7
@@ Line 43: / Line 51: @@
 </pre>
 ==Flags==

Admin: Created page with "{{Main|Ansible/Variables}} {{Main|Ansible/Vaults}} This article covers recommendations and best practices for storing variables (Ansible/Variables) in your vault (Ansi..."

2018-11-15T05:02:26Z

Created page with "{{Main|Ansible/Variables}} {{Main|Ansible/Vaults}} This article covers recommendations and best practices for storing variables (Ansible/Variables) in your vault (Ansi..."

New page

{{Main|Ansible/Variables}}

{{Main|Ansible/Vaults}}

This article covers recommendations and best practices for storing variables ([[Ansible/Variables]]) in your vault ([[Ansible/Vaults]]) while still making it possible to search variable names.

Ansible documentation: https://docs.ansible.com/ansible/latest/user_guide/playbooks_best_practices.html

==Group Variables==

Start with a <code>group_vars/</code> subdirectory that is named after the group you are trying to modify.

Inside of the subdirectory, create two files named <code>vars</code> and <code>vault</code>.

Inside <code>vars</code>, define all variables needed, including any sensitive ones.

Next, copy all sensitive variables over to vault file, prefix them with <code>vault_</code>.

Adjust the variables in the vars file so they point to the matching <code>vault_</code> variables, using Jinja 2 syntax, and ensure that the <code>vault</code> file is encrypted (see [[Ansible/Vaults]]).

==Example==

Directory structure:

<pre>
playbooks/
group_vars/
dbservers/ # name of group
vars # file
vault # file
</pre>

Now suppose we were including the full <code>vars</code> file with sensitive variables and all. It might look like this:

<pre>
host : 0.0.0.0
port : 1234
database_username : root
database_password : strongPassword
slack_api_key : a1a2a3a4a5a6a7
github_api_key : b1b2b3b4b5b6b7
</pre>

==Flags==