Issue #21286 has been updated by Charlie Sharpsteen.
eric sorenson wrote: > > It seems like the simplest fix would be to change the current check so that > > it avoids processing events if `resource.noop?` returns true. > > +1 could you give this a try and we'll see if it breaks anything? Sure, I'll try to write a pull request next week. ---------------------------------------- Bug #21286: noop => true is ignored when resource is triggered by other resource https://projects.puppetlabs.com/issues/21286#change-97191 * Author: Mariusz Gronczewski * Status: Accepted * Priority: High * Assignee: Charlie Sharpsteen * Category: transactions * Target version: * Affected Puppet version: 3.1.1 * Keywords: refresh noop * Branch: ---------------------------------------- when running : file {'/tmp/asd': content => generate('/bin/date'), notify => Exec['ttt'], } exec { 'ttt': command =>'/bin/date', logoutput => true, noop => true, } exec is still ran even tho it's set to noop, any notify to resource makes it ignore noop parameter: Notice: /Stage[main]//File[/tmp/asd]/ensure: defined content as '{md5}2f61ea5f548d9cfcda74e24a547dfa86' Notice: /Stage[main]//Exec[ttt]/returns: current_value notrun, should be 0 (noop) Notice: /Stage[main]//Exec[ttt]/returns: Tue Jun 18 14:12:15 CEST 2013 Notice: /Stage[main]//Exec[ttt]: Triggered 'refresh' from 1 events Notice: Finished catalog run in 0.99 seconds -- 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.
