On Fri, May 18, 2012 at 12:44 PM, Eytan Daniyalzade <ey...@chartbeat.com> wrote: > Hey, > > I would like to figure out if the latest puppet client run changed the > state of the server, in a programatic way. Essentially, I would like > to achieve what --detailed-exitcodes provides in later versions of > puppet. I am running in master/slave mode. Any suggestions? I have > considered using /var/lib/puppet/state/state.yaml, and checking if > anything more than 'checked' happened. Would that be the right way to > go? > > Thanks, > --Eytan
We aren't using 0.25.x but we do use puppet reports to track puppetrun status. We feed them into foreman, which should still support the older puppet report format (pre-2.6.5), but you might also be able to use puppet-dashboard. (Looks like it does support the older report format: http://downloads.puppetlabs.com/docs/dashboardmanual.pdf.) (The last_run_report should be in the same directory as state.yaml, but you have to enable reports in your puppet.conf). As an aside, the upgrade from 0.25.x to 2.6.x was relatively painless. Perhaps someone else can address your question more directly? -Brian -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@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.
