On Monday, June 23, 2014 10:18:31 AM UTC-7, John Bollinger wrote: > > > > On Friday, June 20, 2014 2:16:03 PM UTC-5, John Bollinger wrote: >> >> >> I think there is potential for a feature such as this, but for the sake >> of argument, what are the advantages of doing it that way, as opposed to >> via classes? >> > > > Also, have you investigated how far in this direction the existing 'alias' > metaparameter can take you? > > it appears as though you can't use Alias for resource dependencies, which is what i'm after. the best "workaround" i have so far, is to use a class in the middle, where i shove all my logic about picking one or the other class that I need, based on a parameter. that does mean that my "meta class" needs to be aware of all the variations.
having a given module provide a masquerading name would allow for anyone to bring a new implementation for an existing module. say puppetlabs-mysql, for example. what prevents me to create jthuau-mysql-better (not that I can do better) and use that as a drop-in replacement for puppetlabs-mysql ? if i could say "i have this module over here, that can replace this other one", without necessarily have to choose globally which one i use (maybe there are cases where i only want puppetlabs-mysql). for the record, i'm liking where this is going. a simple "alias" feature (without pushing it too far) would be a great benefits, methinks, even if i need to spend some time scratching my head if i mess up something... -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/d08b6680-666d-484a-bc96-a8452e80d02f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
