Issue #6526 has been updated by Nigel Kersten.
Status changed from Unreviewed to Rejected
This should have been called out as part of the release notes, but we're not
going to reimplement it.
Given the way our scoping works, there are all sorts of horrible interactions
here.
You have several options here:
a) Use resource defaults to pick a specific resource
`File { noop => true, }`
b) Use class parameters to set noop as a metaparameter for that class
`class foo ($noop=true) { ... }`
c) File a bug requesting that the Resources resource allow passing through of
the noop metaparameter. This should work but doesn't.
`Resources { noop => true } `
With appropriate variables to control the value of these parameters, you can
achieve exactly the same functionality.
----------------------------------------
Bug #6526: $noop metaparameter no longer works
https://projects.puppetlabs.com/issues/6526
Author: Kal McFate
Status: Rejected
Priority: Normal
Assignee: Nigel Kersten
Category:
Target version:
Affected Puppet version: 2.6.4
Keywords:
Branch:
In 0.24.6 you could use $noop = true to specify no-op mode at top level or per
class (taken from the Pulling Strings book.) This no longer seems to work in
any scope in 2.6.4. I have tried many permutations and all seem to ignore the
value of $noop.
--
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.
