Issue #6847 has been updated by Adrien Thebo. Branch set to https://github.com/puppetlabs/puppet/pull/1783
---------------------------------------- Bug #6847: Cannot read client $noop setting https://projects.puppetlabs.com/issues/6847#change-95827 * Author: John Crenshaw * Status: Merged - Pending Release * Priority: Normal * Assignee: * Category: settings * Target version: 3.3.0 * Affected Puppet version: * Keywords: * Branch: https://github.com/puppetlabs/puppet/pull/1783 ---------------------------------------- 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
