On Jun 8, 2010, at 8:54 PM, Trevor Vaughan wrote:
All,How does this work in the case of multi-party development? For instance, you now have the Module Forge (woo), but I'm sure you're going to get two modules with a 'service { "mysql"' or somesuch. I know that it's easy to say "just be careful", but throwing up the overworked puny human SA defense, not conflicting on duplicate names is going to cause a massive amount of headache in my opinion. How else could this be solved so that people are not bitten by conflicts? Warnings perhaps?
I think there's a misunderstanding - we're not removing the concept of resource uniqueness, just how it's implemented.
That is, currently the only way Puppet can know if a resource is unique is to require that the type and title are a unique combination, but this works poorly for some types - e.g., ports (in /etc/services) are not uniquely identifiable without knowing the name, port, and protocol (mostly through bad design, IMO, but it's too late now).
What David and Markus are talking about is enhancing the concept of uniqueness to enable Puppet to uniquely identify resources by a combination of multiple attributes.
Thus, you'll still get failures if two modules specify the same resource - it's just the mechanism for validating this is being enhanced a bit.
-- He attacked everything in life with a mix of extraordinary genius and naive incompetence, and it was often difficult to tell which was which. -- Douglas Adams --------------------------------------------------------------------- Luke Kanies -|- http://puppetlabs.com -|- +1(615)594-8199 -- You received this message because you are subscribed to the Google Groups "Puppet Developers" 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-dev?hl=en.
