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. 

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/4a8195d5-e5b7-4751-99e5-86601627198e%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to