On 2015-01-10 23:11, Alan McKinnon wrote:
On 10/01/2015 21:40, Tomas Mozes wrote:
Ansible is a not a backup solution. You don't need to download your
/etc
from the machines because you deploy your /etc to machines via
ansible.
I was also thinking about putting /etc in git and then deploying it
but:
- on updates, will you update all configurations in all /etc repos?
- do you really want to keep all the information in git, is it
necessary?
The set of fileS in /etc/ managed by ansible is always a strict subset
of everything in /etc
For that reason alone, it's a good idea to back up /etc anyway,
regardless of having a CM system in place. The smallest benefit is
knowing when things changed, by the cm SYSTEM or otherwise
For what reason?
And how does a workflow look like then? You commit changes to your git
repo of ansible. Then you deploy via ansible and check the /etc of each
machine and commit a message that you changed something via ansible?
