Issue #19878 has been updated by Charlie Sharpsteen.

Category set to language
Status changed from Unreviewed to Investigating
Keywords changed from customer  to notice refreshonly customer 

There are currently some major architectural issues with how refresonly works 
for exec resource (ref. #5876). The extent to which these would affect Notice 
resources would by dictated by how notice is used in dependency chains. Will 
attempt to gather information while de-tangling #5876.

----------------------------------------
Feature #19878: notice refreshonly ability
https://projects.puppetlabs.com/issues/19878#change-90456

* Author: Robert Pearce
* Status: Investigating
* 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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to