It turns out that it was happening, but getting buried in the logs on the server.
I suppose that I was expecting something to come up on the client as most other warnings and errors do. I understand that a function is a server-side object, but if I 'raise Puppet::ParseError' it certainly shows up on the client. Is there any way to propagate this warning to the client output log? Thanks, Trevor On Wed, Sep 9, 2009 at 19:28, Luke Kanies <l...@madstop.com> wrote: > > On Sep 9, 2009, at 1:41 PM, Trevor Vaughan wrote: > >> >> All, >> >> I apologize for asking the question since I know I've done this >> before, but...does anyone know how to emit warnings in a custom >> function? >> >> I tried Puppet.warning, but that didn't appear to print a warning >> message anywhere. > > It... should. That's exactly how we do all of our warnings and such. > Do you just get a no-op on that? > > -- > The big thieves hang the little ones. -- Czech Proverb > --------------------------------------------------------------------- > Luke Kanies | http://reductivelabs.com | http://madstop.com > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
