> > I am in the design and testing phase working on various configurations > and options. > > I generate my configuration files programmatically once a day based on > queries to an asset management database to organize servers a specific way. > There was discussion of a design option that would have a few of hundred > entries in the modulepath day one and grow from there (creating new ones > if needed when the configuration files are generated).. > I don't want to start down a path that could limit me down the road and > require starting over and since I could not find a limit in the puppet > documentation so I thought I would ask. > > I don't see a limit to the module path number enforced in the code, but I am fairly confident that 100s of module path entries is probably not the best solution and searching those module paths is likely to have negative performance impacts.
What is the problem you are hoping to solve with module paths? If you can explain a bit more about how and why, you got to that design, hopefully we can be more helpful. Cheers, Andrew --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
