-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
>> I'm guessing I'll have to write my own to do that -- does anyone have
>> any examples of logging the error message and also adding it to the
>> report object? (... and I don't really want to use the exec {
>> "/bin/false": } workaround)
>
> Digging through the code it looks like puppet adds messages internally
> using Puppet.warning(), Puppet.error(), so I made a custom function to
> call these directly.
>
> I'm still not getting my error() messages in the report yaml ... why?
Probably, because functions are evaluated on the master, while the
report is created on the client when the catalog is applied. So these
messages never get sent down the client...
~pete
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk4oOb0ACgkQbwltcAfKi3+UkgCfVa2tz5Nr6NyklpBwgGuHMoNL
klQAoICzzOX7fckqU//hHxRSGFj8tskV
=1kTp
-----END PGP SIGNATURE-----
--
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.
