Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split group_vars/ENVIRONMENT into smaller files #133

Closed
nathanielks opened this issue Feb 25, 2015 · 3 comments
Closed

Split group_vars/ENVIRONMENT into smaller files #133

nathanielks opened this issue Feb 25, 2015 · 3 comments
Milestone

Comments

@nathanielks
Copy link
Contributor

Hey all-

Was reading up on group variables and realized they can be split into smaller files. Feast your eyeballs: http://docs.ansible.com/intro_inventory.html#splitting-out-host-and-group-specific-data.

This would be great in the context of wanting to separate things out for security concerns as we could set the project up to more easily be used by ansible-vault. Just a thought!

@swalkinshaw
Copy link
Member

Any proposals for new files?

@nathanielks
Copy link
Contributor Author

@austinpray LOL.

@swalkinshaw I've been thinking about this and have a few different ideas. First would be the simplest, have a main.yml and an encrypted.yml. Store everything you don't mind in plaintext in main, everything that needs to be secure in encrypted ( could solve our nginx ssl storage issue? ). Second would be scope it based on roles. If a role doesn't need vars overridden, don't add another file. Examples below.

First:

group_vars/development/main.yml
group_vars/development/encrypted.yml

Second:

group_vars/development/wordpress-sites.yml
group_vars/development/php.yml
group_vars/development/nginx.yml

@swalkinshaw
Copy link
Member

We'll revisit this once the deploys PR and some cleanup is done. Roles/playbooks are changing due to deploys anyway but I think it makes sense to have the vars split up more.

@swalkinshaw swalkinshaw added this to the 1.0.0 milestone Jul 19, 2015
swalkinshaw added a commit that referenced this issue Aug 19, 2015
swalkinshaw added a commit that referenced this issue Aug 25, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants