Is there a limit to the length of the name of a class?
- puppetmaster/clients 0.24.5 on Debian Etch
- clients 0.24.4 on Ubuntu Hardy
- clients 0.24.5 Mac OS X (Leopard)
I have one
class one::two::threeeeee::four { ...usefullthings... }
which does not get evaluated.
If I change that to:
class one::two::threeeeeefour { ...usefullthings... }
it gets evaluated.
The limit might be in the number of "nesting levels" or how the '::'
are called. Does this exist or have I found a bug?
Thanks once again,
udo.
--
---[ Institute of Cognitive Science @ University of Osnabrueck
---[ Albrechtstrasse 28, D-49076 Osnabrueck, 969-3362
---[ Documentation: https://doc.ikw.uni-osnabrueck.de
> Hello once again.
>
> Is there a limit to the length of the name of a class?
> - puppetmaster/clients 0.24.5 on Debian Etch
> - clients 0.24.4 on Ubuntu Hardy
> - clients 0.24.5 Mac OS X (Leopard)
>
> I have one
> class one::two::threeeeee::four { ...usefullthings... }
> which does not get evaluated.
> If I change that to:
> class one::two::threeeeeefour { ...usefullthings... }
> it gets evaluated.
>
> The limit might be in the number of "nesting levels" or how the '::'
> are called. Does this exist or have I found a bug?
I have class and define names waaay (;) longer than that in my
manifest tree (using a 0.23 pm admittedly), so i would expect that you
have a problem somewhere else in your manifest file.
For example, I have class names like
semantico::deployments::customer::blah::app1 - I have not seen the
issue you mention.
Regards,
Mike