Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: PUP 4.3.2
-
Component/s: Language
-
Labels:None
-
Template:customfield_10700 116591
-
Epic Link:
-
Story Points:3
-
Sprint:Language 2016-02-24
-
Release Notes:Bug Fix
-
Release Notes Summary:Our old foe :undef turned up again due to 3.x calling convention also applying to resource expressions.
Description
The following code:
define test ($b) {
|
$a = { key => undef }
|
notice("a: $a") |
notice("b: $b") |
$a.each |Array $values| {
|
notice("a values: $values") |
}
|
$b.each |Array $values| {
|
notice("b values: $values") |
}
|
}
|
|
|
$a = { key => undef }
|
test { "test": |
b => $a,
|
}
|
generates the following output if run with puppet apply:
puppet apply test.pp
|
Notice: Scope(Test[test]): a: {key => }
|
Notice: Scope(Test[test]): b: {key => }
|
Notice: Scope(Test[test]): a values: [key, ]
|
Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Method call, block parameter 'values' expects an Array value, got Tuple at /home/rvicinus/test.pp:8:5 at /home/rvicinus/test.pp:14 on node puppetmaster
|
I would expect that the second each statement would run like the first, because the supplied hash is absolutely equally created like the one provided to the first each statement. I think somehow assigning the hash to a parameter messes up the data types, because the code works as expected if the Array keyword in the second each statement is removed. This is also the workaround that I use.
Attachments
Issue Links
- relates to
-
-
- Closed
-
- links to
