If infrastructures are to be treated as a code than projects that manage them must be treated as software projects. As your infrastructure code gets bigger and bigger you have more problems to deal with it. Code layout, variable precedence, small hacks here and there. Therefore, organization of your code is very important, and in this repository you can find some of the best practices(in our opinion) to manage yours infrastructure code. Problems that are address are:
* Overall organization
* How to manage external roles
* Usage of variables
* Naming
* Staging
* Complexity of plays
#Ansible Best Practises
If infrastructures are to be treated as a code than projects that manage them must be treated as software projects. As your infrastructure code gets bigger and bigger you have more problems to deal with it. Code layout, variable precedence, small hacks here and there. Therefore, organization of your code is very important, and in this repository you can find some of the best practices(in our opinion) to manage yours infrastructure code. Problems that are address are:
* Overall organization
* How to manage external roles
* Usage of variables
* Naming
* Staging
* Complexity of plays
* Encryption of data(e.g. passwords, certificates)
##TL;DR
...
...
@@ -29,7 +29,7 @@ This is the directory layout of this repository with explanation.
development.ini # inventory file for development stage
test.ini # inventory file for test stage
vpass # ansible-vault password file
# This file shoul not be commited into the repository
# This file should not be commited into the repository
# therefore file is in ignored by git
group_vars/
all # variables under this directory belongs all the groups
