It appears that --report only works to send reports to puppetmaster. Is there a way or could an option be added to have the puppet client print out it''s report to stdout or stderr, for folks who are using puppet without the puppetmaster/puppetd? Thanks, Abe _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users
On Jul 17, 2007, at 5:14 PM, aberoham@gmail.com wrote:> > It appears that --report only works to send reports to puppetmaster. > > Is there a way or could an option be added to have the puppet > client print out it''s report to stdout or stderr, for folks who are > using puppet without the puppetmaster/puppetd?It would need to be added, but it should not be too difficult. Would you just want the report stored on the local file system, or sent to a server? And how would you prefer to choose between the two? Please open an enhancement request with this information. Note that you can already use --summarize to get a, well, summary of the transaction report. -- He played the king as if afraid someone else would play the ace. --John Mason Brown --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
I tried "--summarize" and got back: [root@server ldap]# puppet -V 0.22.4 [root@server ldap]# puppet --summarize -v ./main.pp /usr/bin/puppet: unrecognized option `--summarize'' Try ''/usr/bin/puppet --help'' [root@server ldap]# An option to send the report to syslog, the console, or a log file would be perfect. I''ll open an enhancement request. Abe On 7/17/07, Luke Kanies <luke@madstop.com> wrote:> > On Jul 17, 2007, at 5:14 PM, aberoham@gmail.com wrote: > > > > > It appears that --report only works to send reports to puppetmaster. > > > > Is there a way or could an option be added to have the puppet > > client print out it''s report to stdout or stderr, for folks who are > > using puppet without the puppetmaster/puppetd? > > It would need to be added, but it should not be too difficult. Would > you just want the report stored on the local file system, or sent to > a server? And how would you prefer to choose between the two? > > Please open an enhancement request with this information. > > Note that you can already use --summarize to get a, well, summary of > the transaction report. > > -- > He played the king as if afraid someone else would play the ace. > --John Mason Brown > --------------------------------------------------------------------- > Luke Kanies | http://reductivelabs.com | http://madstop.com > > > _______________________________________________ > Puppet-users mailing list > Puppet-users@madstop.com > https://mail.madstop.com/mailman/listinfo/puppet-users >_______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users
On Jul 17, 2007, at 6:32 PM, aberoham@gmail.com wrote:> I tried "--summarize" and got back: > > [root@server ldap]# puppet -V > 0.22.4 > [root@server ldap]# puppet --summarize -v ./main.pp > /usr/bin/puppet: unrecognized option `--summarize'' > Try ''/usr/bin/puppet --help'' > [root@server ldap]#This feature was added in 0.23.0; sorry.> An option to send the report to syslog, the console, or a log file > would be perfect. I''ll open an enhancement request.What would you want sent? The only thing in a report is the same messages that are already going to syslog/console/log file plus some metrics. -- I am a kind of paranoiac in reverse. I suspect people of plotting to make me happy. --J. D. Salinger --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com