Facts and Stored Configs

[Richie Rees]

So finally playing with PuppetDB and have to say its impressive. Planning on extending it slightly to be a CMDB. With that in mind, we produce test systems for developers to test the equipment they are developing on. So these systems are rapidly deployed then torn down. A requirement has been given to me to keep a snap shot of the systems and there configuration, so identical systems can be deployed at a later date. 

The systems have internally developed components each individually configured.  Currently config files are delivered via templates and foreman ENC.  So what I was thinking is can I write a fact that would effectively store all the config files as strings. These could then be recovered at a later date if required.  What would be the pitfalls of doing this, and can anyone think of a better way ?

Thanks,

RIchie. 

[Richie Rees]

Ok scratch that I have just read about "Executable Facts" so I can write a program that will recursively look in the directory structure for the configuration files than pass back the config options as key pairs so this will even track changes over time. Got to hand it to puppetdb its an awesome bit of kit :)