Jira (PUP-7347) Loopup function merge behaviour is not optional.

[Henrik Lindberg (JIRA)]

Title: Message Title

Henrik Lindberg commented on PUP-7347   Re: Loopup function merge behaviour is not optional. The documentation shows how this is done; you either use the most flexible form of lookup call where all values are given as options in a hash, or use the lambda form. You can not, as your post suggests, simply skip the <MERGE_BEHAVIOR> as an argument in the call that requires that in the signature (you have two commas next to each other). You can however use undef there. The examples below are equivalent: lookup('lookup_name', String, undef, 'example string') lookup ('lookup_name',String) |$key| { 'example string' } lookup ('lookup_name', { value_type => String, default_value => 'example string'}) Add Comment   This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.