Module names - limitations / reserved words?

[KnightOrc]

Greeting,

I'm attempting to solve a mystery we had with a puppet module we
couldn't get to auto load.

The module named / folder was called "nfs"

We notice when we ran 'puppetmasterd --no-daemonize --verbose' that
when the client connected that our 'nfs' module was not being auto
loaded.

We reviewed and triple checked our syntax. We located no errors. As a
result of the module not being loaded we were unable to access a
resource defined within the init.pp.

Finally as a "Hail Mary" we renamed the module to 'nfsexports'. On
the next client run the module was auto loaded and all was well in
puppet land.

My question today is, Are there "reserved" words that can't be used as
module to resource names? If yes, does anyone have the list or a URL
to the list? We've looked but all we found are references to class
name limitations, "ie can't begin with a CAPTIAL letter".

Thanks in advance,


Wade

[ndenev]

I think I've hit similar problem, and the issue really was that I was
trying to include a class in a subclass when both have the same name.
I.e.

class baseclass::apache {
include apache
}

This include will reference the baseclass:apache class, and not the
apache class, to work
around it you should use :

class baseclass::apache {
include ::apache
}

Then I've found this thread/bugreport that explains it all :
http://www.mail-archive.com/puppe...@googlegroups.com/msg03637.html
But I agreee that it should probably it should print a warning or
something.

Regards,
Nikolay

[Peter Meier]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> Then I've found this thread/bugreport that explains it all :
> http://www.mail-archive.com/puppe...@googlegroups.com/msg03637.html
> But I agreee that it should probably it should print a warning or
> something.

can you file a feature request?

~pete
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkzT1sYACgkQbwltcAfKi39giwCfVgGFrZ2T36k9gxrgeiBl52HJ
bN8AniIyKS1b20wHw1yqcxAaORhT0iDg
=GLZv
-----END PGP SIGNATURE-----

[ndenev]

On Nov 5, 12:04 pm, Peter Meier <peter.me...@immerda.ch> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> > Then I've found this thread/bugreport that explains it all :
> >http://www.mail-archive.com/puppe...@googlegroups.com/msg03637.html
> > But I agreee that it should probably it should print a warning or
> > something.
>
> can you file a feature request?
>
> ~pete
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)

> Comment: Using GnuPG with Mozilla -http://enigmail.mozdev.org/

>
> iEYEARECAAYFAkzT1sYACgkQbwltcAfKi39giwCfVgGFrZ2T36k9gxrgeiBl52HJ
> bN8AniIyKS1b20wHw1yqcxAaORhT0iDg
> =GLZv
> -----END PGP SIGNATURE-----

I've filed a feature request : http://projects.puppetlabs.com/issues/5208
with a typo and messed up links...

Regards,
Nikolay
Next time I'll click "Preview" first :)