On 01/24/2012 12:38 PM, Tim Sharpe wrote: > The only "clean" way to handle this that I can think of off the top of > my head > is for Puppet to start silently discarding duplicate definitions and > just using > the first one it comes across (with perhaps a message being logged at info > level so that it's not completely invisible). > > This is far from ideal but so are the other proposed solutions so far :)
No, it really adheres to KISS very nicely. This reminds me of the discussion of how resource defaults should stack when they combine from different scopes. (How did that turn out, anyway?) The vision here would probably be that the compiler collects all definitions or the same resource, and only dies if any attributes differ. Sadly, *due* to resource defaults, this could be more likely than one would think. Also, depending on how the compiler is implemented, it may be Very Hard to do. Cheers, Felix -- 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.
