On Thursday, May 16, 2013 5:10:44 PM UTC-5, Matt Zagrabelny wrote: > > Greetings, > > When writing modules are people namespacing them to avoid collisions > with puppetlabs' modules? >
Typically not. > > I wrote some (very simple) modules: > > mysql > postgresql > > that now have namespace conflicts when I am trying to install the > puppetlabs modules of the same name. > > Is there a best practice or style guide that people follow when > namespacing their in-house modules? > Not that I know of. Prevailing opinion seems to be that you should choose one module to manage each type of subsystem for all nodes in your site, or at least for all nodes in any given environment. If you follow that practice then a name collision highlights a poor choice of names for one module or another. On the other hand, there's a slightly-different question involving modules and classes providing *extra*, site-specific configuration and/or customization for one subsystem or another. Personally, I am inclined to put such stuff into classes in a 'site' module. E.g. "site::mysql". Inasmuch as such a module provides site-specific declarations and data, it's not much of a stretch after all to say that putting its contents into generically named modules, such as "mysql", would constitute a poor naming choice. 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
