Jira (PUP-6064) Optional type misinterpreted by epp() and inline_epp() in puppet 4.4.0

[Francois Lafont (JIRA)]

Title: Message Title

Francois Lafont created an issue   Puppet / PUP-6064 Optional type misinterpreted by epp() and inline_epp() in puppet 4.4.0 Issue Type: Bug Affects Versions: PUP 4.4.0 Assignee: Unassigned Components: AIO Created: 2016/03/17 3:50 AM Labels: puppet-agent Priority: Normal Reporter: Francois Lafont Here is the code to realize the problem. inline_epp( '<%- |Optional[String[1]] $var| -%>', { 'var' => undef } ) The value undef is given to the variable var and it should be accepted by the function inline_epp() because the type of var is: Optional[String[1]] which means ok to have a value undef. But with Puppet 4.4.0, we have an error: ~# puppet --version   ~# puppet apply /tmp/test.pp Error: Evaluation Error: Error while evaluating a Function Call, lambda: expects a value for parameter 'var' at /tmp/test.pp:1:1 on node puppet.athome.priv We have exactly the same error with the function epp(). Note: with Puppet 4.3.2, the same worked correctly: ~# puppet --version 4.3.2   ~# puppet apply /tmp/test.pp Notice: Compiled catalog for middleware.athome.priv in environment production in 0.04 seconds Notice: Applied catalog in 0.12 seconds Add Comment   This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.