----- Original Message -----
> On Thu, Jan 6, 2011 at 2:19 PM, R.I.Pienaar < [email protected] > wrote:
> 
> 
>> imho the right solution is a combination of the require and include
>> keywords,resources requiring classes used extremely sparingly and the new
>> syntax as Danpointed out.
>> 
>> What worries me greatly is that 'use parametrized classes' for
>> everything
>> recommendation seems to be the default response these days from PL
>> even to the
>> point of suggesting the include and require keywords be removed and
>> deprecated
>> while the alternatives are, to be frank, half baked.
> 
> 
> 
> We have some serious language issues with the combination of
> "include/require" being able to repeatedly operate on a class, and the
> new parameterized syntax only letting you operate on a class once.
> 
> 
> I'm not convinced what the right answer is yet. This is why the
> following bug is still in the "Needs Design Decision" stage.
> 
> 
> http://projects.puppetlabs.com/issues/5046
> 
> 
> It's possible we just made a mistake with parameterized classes as
> implemented in 2.6.x. We do need to get to somewhere *consistent*, I'm
> just not quite sure what that place looks like yet.
> 


Then I am doubly perplexed.  It's not a surprise that the feature isn't 
adequate perhaps even mistake has been made.

Being that it is not done or fixed in stone you're almost guaranteed
that its behavior, implications, perhaps even the syntax will change in future
versions.  And not just superficially either, its far from workable.

Does it serve the users that we are recommending they use such a feature?
Do we not almost guarantee costly from a time and effort and risk basis
that using this feature will result in a very difficult migration to a future
version of puppet?

It's loose loose, the users loose since the Lynchpin of their production 
systems - configuration management - is a ever moving target requiring heavy
refactors between versions.  The community who support the opensource users
loose because it's ever more complex to support the number of puppet versions
out there - they all behave differently.

> It spreads confusion and frustrates users.

I'd just state this again.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Reply via email to