Well we had that problem in the past. I now name my modules with a
prefix for the company first letter so if I was working for puppetlabs
then I would name the module pmysql. The thing is that most of the time
I want convenient wrappers for the mysql module provided by puppetlabs
or some third
Hi Matt,
What I've seen done before is to use ${modulename}x for 'wrapper' modules
that give you the ability to stay current with the
forge/release/externally-owned module, but still maintain the necessary
site-spectific-shim code to extend the functionality of the original module
in the ways you
Greetings,
When writing modules are people namespacing them to avoid collisions
with puppetlabs' modules?
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
