Details
-
Bug
-
Status: Needs Information
-
Normal
-
Resolution: Unresolved
-
PUP 3.7.3, PUP 3.8.5, PUP 4.3.2, PUP 5.5.12, PUP 6.12.0
-
None
-
Coremunity
-
Minor
-
47711
-
1
Description
This behavior is really quirky.
It seems if a defined type is restructured to include the noop parameter, you get the expected behavior described initially in the ticket (ie a noop overwrite). Without restructuring the defined type, noop => false will not take precedence over what is set in let's say site.pp. This could be due to an issue with the way noop is being "inherited" by the resources with the defined type. I am using inherited pretty loosely here, as this isn't actually the way this works.
Attachments
Issue Links
- blocks
-
MODULES-2741 Noop attribute does not work with Concat resources
-
- Closed
-
- is duplicated by
-
PUP-10301 noop metaparam on defined ignored inside of classes
-
- Closed
-
-
PUP-6743 Classes should propagate schedule metaparameter to its contained resources
-
- Accepted
-
- relates to
-
PUP-1675 Incorrect Warning issued when assigning $noop as class variable
-
- Closed
-
-
MODULES-6817 concat : resource metaparameter noop don't work
-
- Closed
-
- links to