Jira (PUP-4016) Consider short circuiting data binding if lookup is called as the default value
Title: Message Title Henrik Lindberg commented on PUP-4016 Re: Consider short circuiting data binding if lookup is called as the default value The alternative is to solve this on the data side - e.g. to add metadata for a key to specify its lookup behavior (merge strategy with parameters etc.). (I actually like that solution better - it does require new hiera backend implementations though). Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-4016) Consider short circuiting data binding if lookup is called as the default value
Title: Message Title Daniele Sluijters commented on PUP-4016 Re: Consider short circuiting data binding if lookup is called as the default value I'm not overly enthusiastic with the prospect of shoving function calls back into class parameters again. Wasn't that part of what we were trying to combat with data bindings? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-4016) Consider short circuiting data binding if lookup is called as the default value
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-4016 Consider short circuiting data binding if lookup is called as the default value Issue Type: New Feature Assignee: Unassigned Components: DSL Created: 2015/02/15 3:49 PM Fix Versions: PUP 4.0.0 Priority: Normal Reporter: Henrik Lindberg With the new data provider support ( PUP-1640 ), and the new lookup function (PUP-3948) we have a very good story for how to handle data binding and lookup. One feature that is asked for over and over again is the ability to perform automatic data binding of class parameters using other lookup strategies than 'priority'. Users try to achieve this by making a call to either hiera_hash or hiera_array and they are then surprised when these functions are not called. What they must do is bind a different key in data (to avoid the automatic lookup, and instead use the default value _expression_ for the parameter. A solution to this could be to say that a parameter that has a default value _expression_ that is a call to `lookup` uses this _expression_ instead of the automatic l
