Issue #7987 has been updated by Daniel Pittman.

> Whilst implicit, the current search “magic” described in the documentation
> is somewhat restrictive. Rather than having the definitions in init.pp or
> the exact logical path, e.g. class::subclass::subsubclass =>
> modules/class/subclass/subclass.pp the path should be searched up wards from
> the exact location to init.pp, e.g:
>
> * modules/class/subclass/subsubclass.pp
> * modules/class/subclass.pp
> * modules/class.pp
> * modules/init.pp
>
> In my own use case I have a ::server and a ::client subclass for a number of
> classes, due to wanting to improve the organisation away from just having a
> single init.pp I am instantly forced to expand the layout to the fullest
> possible, with one file per class. I would much rather have a single pp file
> to hold both the ::server and ::client to ease management (a single file can
> be copied, not a directory tree)

You should be ably to add an `init.pp` to the top of your module, then
`import` whatever other manifest layout you want.  That should let you
have the server / client split, without needing to have the current
class / file mapping changed.  Which might be a suitable work-around
for you?
----------------------------------------
Bug #7987: Module search magic should be improved
https://projects.puppetlabs.com/issues/7987

Author: Chris Phillips
Status: Unreviewed
Priority: Low
Assignee: 
Category: modules
Target version: 
Affected Puppet version: 2.6.7
Keywords: 
Branch: 


Whilst implicit, the current search "magic" described in the documentation is 
somewhat restrictive. Rather than having the definitions in init.pp or the 
exact logical path, e.g. class::subclass::subsubclass => 
modules/class/subclass/subclass.pp the path should be searched up wards from 
the exact location to init.pp, 
e.g:

modules/class/subclass/subsubclass.pp
modules/class/subclass.pp
modules/class.pp
modules/init.pp

In my own use case I have a ::server and a ::client subclass for a number of 
classes, due to wanting to improve the organisation away from just having a 
single init.pp I am instantly forced to expand the layout to the fullest 
possible, with one file per class. I would much rather have a single pp file to 
hold both the ::server and ::client to ease management (a single file can be 
copied, not a directory tree)





-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/puppet-bugs?hl=en.

Reply via email to