You could always have a script that queries the puppetmaster or whatever your report server is. I'd just use https. Have some cgi script that grabs the latest yaml file for the requesting host and then returns it. The requesting script on the client can then parse it and do whatever with it. You could get crazy and cache the report locally but you'd need some way of dirtying it after each puppet run. I don't think there's any security implications in that. You shouldn't have any sensitive data in your reports unless you log the output of Execs that contain passwords.
On Aug 22, 2010, at 8:52 AM, Chris <sinl...@gmail.com> wrote: > Hi > > Is there a way to parse the yaml reports on locally on the puppet > clients. What I'd like to offer our sysadmins is a command that will > give them some info when the last puppetrun was and whether anything > has changed. This could be included in .profile/.bashrc. We have an > environment where admins look after a their "own" machines. And it is > new that something like puppet ist allowed to interfer with "their" > systems so we are slowly getting used to the new situation. I do hope > that we will eventually move to a centralized reporting UI. We're just > not that far yet. > > > Thanks for any help > > > Chris > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
