----- Original Message ----- > > > > On Tue, Apr 12, 2011 at 12:54 AM, R.I.Pienaar < r...@devco.net > > > wrote: > > ----- Original Message ----- > > > > > > > > > > > > On Mon, Apr 11, 2011 at 9:25 PM, John Warburton < > > > jwarbur...@gmail.com > wrote: > > > > > > > > > OK, I'll bite > > > > > > In the newly published Style Guide ( > > > http://docs.puppetlabs.com/guides/style_guide.html ), right at > > > the > > > end it says > > > > > > Modules should avoid the use of extlookup() in favor of ENCs or > > > other > > > alternatives > > > > > > > > > For clarity, this should read: > > > > > > in favor of ENCs in combination with parameterized classes > > > > > > > > > > > > But there is no reason as to why. > > > > > > > > > that is partly my fault. > > > > > > <the following is my opinion, and may or may not express the > > > opinions > > > of PuppetLabs, although I can be pretty persuasive :) > > > > > > > Extlookup provided some necessary pre-2.6.x functionality, > > > namely, > > > a > > > sane way to get around dynamic scoping. > > > > This is not what extlookup is for. Yes it effectively works around > > the Wacky Scope problems but that is not its reason for existing. > > > > It exists primarily to: > > > > - allow the data - lets call it the model - to live separate from > > the > > code (controller?) and the templates (view?) > > > > > > Let me clarify this: > > I understand this is not what extlookup is for, I was saying here > > that this is why is was 'necessary' pre 2.6.x (as a sane > > alternative > > to dynamic scoping), I apologize, because obviously my intent here > > was not clear . The kind of data modeling you mention has been > > possible with an ENC for as long as I have been using Puppet. > > Solving this problem with an ENC is suitable for people who can > program. > > You are saying 'puppet cannot do this on its own, please write a > whole > bunch of code in $language to address the shortcoming' is this the > message to send people who do not want to pay someone to come write > that ENC? > > In the context of the question: do we use extlookup to solve this > problem > or do we use an ENC to solve the problem. > > Your answer here is extlookup isnt needed, just write your own ENC. I > am > saying this is a very un newbie friendly message to send to the user > base > when there is a way to solve the problem now while puppetlabs works > on > either a good ENC that we can download or work on finishing the PDL. > > > I completely agree that this recommendation is a little lacking > without an existing ENC to back it up.
<lots snipped where you mostly agree with me that the style guide should be a roadmap doc> so whats the recommendation today for the user base then? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
