Extending the script depends on what yaml files you plan to parse and what serialized objects are contained therein.
http://www.skorks.com/2010/04/serializing-and-deserializing-objects-with-ruby/ On Dec 12, 2013, at 11:07 PM, Stuart Cracraft <smcracr...@me.com> wrote: > Great. > > Okay - anyone additionally, how would you extend Dan's script to dump the > entirety of a Puppet YAML > to a plain text report. > > I know, I know. It sounds boring, painful even but the rationale is to know > exactly > what the YAML says even though it is voluminous. > > The reason? > > Our Security Group would like to have complete visibility to logs in simple > formats they can parse > and understand and socialize it to the C-suite with. Also, it can be used to > analyze Puppet's proposed > operations in noop mode prior to an eventual turnup in full 7x24x365 mode for > selected subsets of > our cloud. > > On Dec 12, 2013, at 8:03 PM, Dan White <y...@comcast.net> wrote: > >> No. >> I whipped that sample up in about 10 minutes. >> >> It provides a starting point for you to develop what you want. “Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us.” Bill Waterson (Calvin & Hobbes) -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/A5133F3F-CAAC-45D3-BD84-8D8CA5A174DF%40comcast.net. For more options, visit https://groups.google.com/groups/opt_out.
