Issue #6847 has been updated by Steve Shipway.
I think the original poster meant bug #6526 ( $noop cannot be assigned ). This bug was rejected because being able to assign to $noop during a manifest would do all sorts of horrible things. However this problem is more being unable to READ the $noop variable , so that you can make manifests behave differently in noop mode -- specifically (in my case) allowing a custom ruby function to suppress actions when in noop mode. I think this functionality (read-only $noop) should be fairly simple to achieve -- there may even be a way to do it in a custom function already, though I wouldnt know what it is... ---------------------------------------- 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.
