The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

Bug #6549

Resources resource should allow passing through of the noop metaparameter.

Added by Kal McFate about 3 years ago. Updated 9 months ago.

Status:AcceptedStart date:03/02/2011
Priority:HighDue date:
Assignee:-% Done:

0%

Category:-
Target version:-
Affected Puppet version: Branch:
Keywords:

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com

This ticket may be automatically exported to the PUP project on JIRA using the button below:


Description

Since using ‘$noop = true’ is no longer an option (see #6526), there should be a way to set global noop within a manifest. This should pass through to all resources but currently doesn’t.

Resources { noop => true }

History

#1 Updated by Ben Hughes about 3 years ago

  • Status changed from Unreviewed to Needs Decision
  • Assignee set to Nigel Kersten

#2 Updated by Nigel Kersten over 2 years ago

  • Status changed from Needs Decision to Accepted
  • Assignee deleted (Nigel Kersten)

All our metaparameters should work with the resources resource.

#3 Updated by Sam Morrison 9 months ago

  • Priority changed from Normal to High

I just tested this out and it seems like setting

Resources { noop => true }

Doesn’t have any affect on anything?

#4 Updated by John Bollinger 9 months ago

Sam Morrison wrote:

I just tested this out and it seems like setting

Resources { noop => true }

Doesn’t have any affect on anything?

That would be because it doesn’t say what you want it to say. It sets a default parameter value for all (meta)resources of type Resources that are declared in the scope of that declaration. That’s not the same as setting a default parameter value for resources of all types. If no Resources resources are declared, then naturally parameter defaults declared for that type have no observable effect.

John

Also available in: Atom PDF