Issue #15652 has been updated by eric sorenson. Status changed from Unreviewed to Duplicate
This is a dup of a very old bug, #3763, which we should re-open. ---------------------------------------- Bug #15652: Service noop => true doesn't work https://projects.puppetlabs.com/issues/15652#change-69262 Author: Hari Sekhon Status: Duplicate Priority: Normal Assignee: Category: service Target version: 2.7.x Affected Puppet version: Keywords: Branch: I have a scenario where puppet is managing config files and services are either subscribed to those files or the files are notifying the service. The file contents need to change it's a non-functional change and I don't want the services to restart. So I initially did `Service { noop => true }` in site.pp but this had no effect the service got restarted anyway. Then I tried in the module class's service definition itself to put `noop => true` but this also didn't work and when the file content changed it restarted the service. noop is a metaparam but it looks like puppet isn't respecting it. I'm running puppet 2.7.12 but I've had this issue way back since I was running 0.24.x. Before anyone says why not just commented out all the subscribe and notify lines, this affects a lot of modules and that would be very inefficient to do. The noop metaparam should theoretically work. Is this a design decision to not respect the metaparam if a dependent resource changes? Surely the metaparam should take precedence to at least give the user the choice. -- 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.
