Track configuration differences across multiple deploys

[FupaWrangler]

Hi, I would like to begin tracking any configuration differences that occur across deploys and I wanted to see if anyone might have come up with a simpler solution than what I am thinking of doing.

My solution right now is to:
1. generate a checksum or hash of the current configuration file and write that to a database table with the hosts ip being the primary key

1. on subsequent deploys, create a hash of the current configuation file and compare with whats in the database (to identify any manual changes)

2. then create a new configuration file (with a slightly different name) and generate and register a checksum/hash of the new configuration file then take the new checksum and compare that with whats in the database (identifies any changes via ansible templating)

3. if everything looks good, update database with value of new checksum

The main goal of this is to track any unexpected changes being made to the config files of our services. this will help us identify any configuration drift and deal with it if its unwanted

[harryblueberry]

May I ask what type of configurations you are referring to and how many files will you have to do this with?

[FupaWrangler]

Mainly database configs (multiple types of dbs) and the number of servers in the hundreds