On 06/19/2014 03:13 AM, Trevor Vaughan wrote: > It just so happens that you can manipulate the catalog once applied to > the system in various parts of custom types and I've hacked around > this a bit by creating random resources as necessary in the past.
Yes, I cringed. "Well" done ;-) I stand by my assertion that we can model many such *resource* crossdependency situations using the virtual resource feature. Enabling conditional class inclusion is the actual holy grail here, I feel. On 06/19/2014 12:22 AM, Joachim Thuau wrote: > What I would be after is the ability to have a module "masquerade" as > a different name. so I can say "require auth" in some moduleA, and > have ModuleAuth1 and ModuleAuth2 both say "I can provide "auth", and > let the manager/user of the system define which one they want. > ... > Now, all that being said, I have absolutely no knowledge of the way > the parser works internally, so this could be very silly, and > completely off the realm of possibilities... Eh, no, that sounds actually pretty neat, but should be the subject of a whole nother thread. I feel that such a feature could be designed independently from the catalog introspection discussion. Cheers, Felix -- 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/53A34592.5060203%40Alumni.TU-Berlin.de. For more options, visit https://groups.google.com/d/optout.
