On Tuesday, July 24, 2012 10:25:12 PM UTC-5, Brian Gupta wrote: > > And is the following the best way to support this: (ie: will it be > supported for the foreseeable future.) > > $modulepath/modulename/manifests/parentclass/subclassname.pp the way > the autoloader supports this? > > Yes, this is how the autoloader works.
> Long story short, I can test and see if it works, but I don't want to > trust that as a way to see if something is a supported patttern, as > historically many things that work, aren't neccesarily supported. > > Also can and should I have more than one init.pp files in a module? > > e.g. > $modulepath/modulename/manifests/init.pp > $modulepath/modulename/manifests/parentclass/init.pp > > I don't know for sure, but my understanding is that you only have a single init.pp per module, and it should contain a single class with the same name as the module, even if that is an empty class. > I did a bit of reading in the puppetdocs, and it seems where i am > using parentclass, there is a namespace feature called > "implementation", which basically allows one to extend the namespace, > but it is unclear if "implementation" can also be a class? From docs: > "This directory’s name affects the class names beneath it." > > I believe I don't need both to be supported, and am largely looking at > this as a way to organize some of our overloaded modules, that don't > make sense to be broken out into separate modules. > > Thanks, > Brian > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/AeG2mH8ZQW0J. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
