Issue #6766 has been updated by konrad rzentarzewski.

that's fair to me, altough i don't feel like there should be 2 types of Notify 
- one that logs as changes and the other that doesn't.

a background for this change for us is that we use a custom report to nagios 
which (among other things) checks if given node is marked as "noauto" (this 
effects in that puppetd on that node is running with noop). this way we're 
alerted is any change on the node is pending, but the change is not being 
applied automatically. we prefer to use it on critical infrastructure to keep a 
benefit of site-wide settings and doing changes in controlled manner (only 
senior staff has access to the nodes and can apply the changes by manually 
reviewing them and running puppetd without noop parameter by hand).

this is basically a reason why we prefer only real changes appear as changes in 
reports (ie. we use onlyif parameter for Exec extensively to ensure that it's 
triggered only when needed). Notify is a only resource i know which works this 
way.
----------------------------------------
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.

Reply via email to