Issue #4915 has been updated by Andrew Parker.
Target version deleted (2.7.x)
Removing the target version, since this was done as a documentation change.
Issue #15756 is the one about making puppet stricter about this.
Bug #4915: scope.function_extlookup
Issue #4915 has been updated by Andrew Parker.
Nick, I know this bug is from a long time ago, but functions were always
supposed to be passed an array when called from ruby code. It was a fluke of
the function and ruby 1.8 that it sometimes worked. There is a change in 3.0.0
that asserts tha
Issue #4915 has been updated by Nick Fagerlund.
It's not obvious to me where or how this should be documented. Does this affect
any other functions that take more than one argument? If not, why not -- what
makes extlookup the special case? (And has there been any progress on Nigel's
decision
Issue #4915 has been updated by James Turnbull.
Category set to documentation
Assignee set to Nick Fagerlund
Target version set to 2.7.x
Nick - can you please update the docs as discussed.
Bug #4915: scope.function_extlookup (in templates) takes an array
Issue #4915 has been updated by Jordan Sissel.
Agreed. Two things - update the docs for how to call it and also have the
extlookup() function return a sane error message saying "Pass an array, not a
string" or something otherwise indicative of what was done wrong.
--
Issue #4915 has been updated by R.I. Pienaar aka Volcane.
Markus Roberts wrote:
> I've removed the part of the ticket that duplicates #4549.
>
> That leaves the question: is this actually a bug, or just poor documentation
> of how to call extlookup from within a template? I'd lean towards the
