Issue #19878 has been updated by Charlie Sharpsteen. Status changed from Investigating to Duplicate
Closing as a duplicate of #651 which proposes creating a `refreshonly` metaparameter that would be available to all types. ---------------------------------------- Feature #19878: notice refreshonly ability https://projects.puppetlabs.com/issues/19878#change-94212 * Author: Robert Pearce * Status: Duplicate * Priority: Normal * Assignee: Charlie Sharpsteen * Category: language * Target version: * Affected Puppet version: * Keywords: notice refreshonly customer * Branch: ---------------------------------------- It would be handy if the notice{} resources type had the ability to have 'refreshonly' similar to how exec resources do. Currently, notice{} will always execute, and when it does the enterprise dashboard records this as a change. We have nodes with things like notice { "memory set aside for product X is $blah"} and this records a change on every puppet run. It would be better if you could notify the notice{} resource from elsewhere to control when it actually prints (say, from the product X package resource), and therefore stop dashboard thinking this is a change, when it clearly isn't. -- 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
