Jira (PUP-2845) Move epp() and inline_epp() to 4x function API

[Kurt Wall (JIRA)]

Title: Message Title

Kurt Wall commented on an issue   Re: Move epp() and inline_epp() to 4x function API By visual inspection at SHA=13186fdc06decc690c1d6ad6eef3c0ca9672a8e4 in master, I can confirm that epp.rb and inline_epp.rb have been moved to the Puppet v4 API. In addition, EPP templates appear to work in v4 as they did in v3: <%-| $x, $y, $z = 'default value' |-%> x = <%= $x %> y = <%= $y %> z = <%= $z %> $ be puppet apply -e "notice epp('x.epp', { x=>1, y=>2, z=>undef })" --templatedir . --parser future --disable_warnings deprecations Notice: x = 1 y = 2 z = default value Notice: Compiled catalog for breve.corp.puppetlabs.net in environment production in 0.35 seconds Notice: Finished catalog run in 0.03 seconds $ be puppet apply -e 'with(1,2,3) | Integer *$x | { notice $x }' --parser future --disable_warnings deprecations Notice: [1, 2, 3] Notice: Compiled catalog for breve.corp.puppetlabs.net in environment production in 0.34 seconds Notice: Finished catalog run in 0.04 seconds Add Comment   Puppet / PUP-2845 Move epp() and inline_epp() to 4x function API The {{epp()}} and {{inline_epp()}} functions must be moved to the 4x function API in order to work correctly. The 3x function API requires transformation of all undef/nils to empty string, and that catalog entry types are transformed to Resource references. This does not work well when these values again emerge in Puppet logic. This also blocks the wan... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.