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:
class blah {
exec { danger:
noop => true,
tag => hitme,
command => "might_break_it",
path => "/bin:/usr/bin:/usr/local/bin",
logoutput => true
}
}
And fire up puppetd with
puppetd -o --tags hitme
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".
