Issue #6766 has been updated by Nigel Kersten.
I believe you're looking at this the wrong way around Konrad. Currently the only way to notify on the agent side is to use a notify resource. *Because* it is a resource, and a special one that *always* "changes" so that the message is visible, it shows up as a change. I'm saying that the right way forward is to *not* use a resource to issue notifications on the agent side, precisely because of what you're complaining about. I'm not sure what your line about puppetlabs/community is meant to refer to. ---------------------------------------- Feature #6766: Ability to display messages during agent run without creating resource changes https://projects.puppetlabs.com/issues/6766 Author: konrad rzentarzewski Status: Accepted Priority: Normal Assignee: Category: reports Target version: Telly Affected Puppet version: Keywords: Branch: The problem with the notify {} resource is that it isn't idempotent, and always shows up as a change. Much like notice(), we should have a way to display messages on the agent that are purely informational, without creating changes for the reports. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
