Hi, this is really, really meta (http://xkcd.com/917/).
I'm a little cautious of building something like this: http://thedailywtf.com/Articles/The_Enterprise_Rules_Engine.aspx I'd have to play with your module though in order to get a feel about wether it is rather useful or over the top. One remark about your README - it's true that the adoption of functions is not mentioned in the current documentation, but please note that you can trace past documentations and easily bisect the origin of any specific feature: http://docs.puppetlabs.com/references/3.2.2/function.html http://docs.puppetlabs.com/references/2.7.20/function.html etc. Also, git. :-) Cheers, Felix On 04/27/2014 03:25 PM, John Morton wrote: > I made a module called resource_factory: > > https://forge.puppetlabs.com/jaydub/resource_factory > > It has two parts. One is the resource_factory class, the other is the > defined_resource_factory resource type. They both do the same kind of > thing — wrap around create_resources with a hiera look up on some key. > The difference is that the class creates defined_resource_factory > instances by default, and those instances are where you put the resource > types and hiera keys for the stuff you really want to create. > Everything's configured in hiera without a lot of site specific classes. > > Question is: have I just reinvented the wheel on some existing best > practice, and if so, how are the grown ups creating resources out of Hiera? > > John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/535E1782.6040508%40alumni.tu-berlin.de. For more options, visit https://groups.google.com/d/optout.
