Issue #682 has been updated by luke. Target version changed from 0.25.0 to 0.26.0 Affected version set to 0.24.7
Bumping again, for expediency. ---------------------------------------- Feature #682: Should be able to override noop when set in a type http://projects.reductivelabs.com/issues/682 Author: whaymand Status: Accepted Priority: Normal Assigned to: luke Category: RAL Target version: 0.26.0 Complexity: Unknown Patch: None Affected version: 0.24.7 Keywords: I'm thinking about a configuration class that, amongst other things execs out to a 'dangerous' configuration script. I'd like to make this a noop by default, so the operator has to try a bit harder to invoke it. So I thought about doing something like: <pre> class blah { exec { danger: noop => true, tag => hitme, command => "might_break_it", path => "/bin:/usr/bin:/usr/local/bin", logoutput => true } } </pre> And fire up puppetd with <pre> puppetd -o --tags hitme </pre> Unfortunately it doesn't fire the script... Whilst I see from an earlier post in puppet-users there you can supply --no-noop to puppetd, it makes no difference. I presume this getoptism only works if the noop you're using has been put in puppet.conf, not in the type. This enhancement request is to create a way to override the "noop => true". ---------------------------------------- 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://reductivelabs.com/redmine/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 -~----------~----~----~----~------~----~------~--~---
