2009/10/17 Billy Shaw <bi...@sceneunseen.com>: > 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.
Okay. I suspect there is a limit and that approach probably isn't scalable. Everything under the path is included - so why not expand underneath the path rather than extend the value of the option? Regards James Turnbull -- Author of: * Pro Linux Systems Administration (http://tinyurl.com/linuxadmin) * Pulling Strings with Puppet (http://tinyurl.com/pupbook) * Pro Nagios 2.0 (http://tinyurl.com/pronagios) * Hardening Linux (http://tinyurl.com/hardeninglinux) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
