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 :)
On Friday, 1 November 2013 13:14:41 UTC, Richie Rees
wrote:>
> 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 puppet-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/6ef4567b-206e-41dd-96ab-5ec8802e3e25%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.