Issue #6847 has been updated by Steve Shipway.
This functionality would be of great use to us as well. We have integrated Puppet with the SecretServer software to automatically maintain root passwords (changing after 60 days and update in SecretServer) but the ruby code to update SecretServer is still run when in noop mode, even though the Exec to actually change the password is not! We need some way to detect noop mode from within the manifest. ---------------------------------------- Bug #6847: Cannot read $noop https://projects.puppetlabs.com/issues/6847 Author: John Crenshaw Status: Needs Decision Priority: Normal Assignee: Nigel Kersten Category: Target version: Affected Puppet version: Keywords: Branch: Discovered this when trying to work around the error that caused me to discover #6846. Basically, I needed to be able to detect the "noop" intention to prevent the dry run from erroring out due to some complex dependencies. It looks like per #6525 the $noop variable is no longer available in any form, even for reading. I can understand why changing it at runtime would not be something you want to support, but readonly access doesn't violate the need in #6525 and is pretty important to allow workarounds for situations like this, where not all interdependencies are fully visible to puppet (and therefore the developer is responsible to enforce the noop). For now, I've worked around this by adding FACTER_noop=1 to my command line. It's clunky and redundant, but at least it lets me check my code. -- 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.
