Jira (PUP-9208) Requesting new feature for notify messages

[Henrik Lindberg (JIRA)]

Title: Message Title

Henrik Lindberg commented on PUP-9208   Re: Requesting new feature for notify messages Unfortunately my idea of using deferred does not work without modifications. Given this: notify{ first: message => "first notify" } $x = Deferred('new', [String, Deferred('err', ["oh no"])]) notify{test: message => $x } It will make a normal run + log an error. henrik$ puppet apply test.pp Error: Scope(): oh no Notice: first notify Notice: /Stage[main]/Main/Notify[first]/message: defined 'message' as 'first notify' Notice: Notice: /Stage[main]/Main/Notify[test]/message: defined 'message' as '' Notice: Applied catalog in 0.01 seconds henrik$ echo $? 0 But will exit with 0. If changing the call to err to fail it fails prematurely - like this: henrik$ puppet apply test.pp Error: oh no henrik$ echo $? 1 Then it does not apply anything because fail bailed out. What is missing is a function that will log and cause an exit 1. Ping Josh Cooper Do you think it is possible to write such a function? Sidenote: the double deferred that calls String.new is because err and warning returns nil and notify resource does not like this. The double defferred type casts the nil/undef into a String. Add Comment   This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.278957.1538656473000.130954.1570354800272%40Atlassian.JIRA.