Thanks for the explanation. Sounds like I was way off. -eric
On Nov 11, 10:33 am, "R.I.Pienaar" <r...@devco.net> wrote: > ----- "Eric Snow" <es...@verio.net> wrote: > > > Thanks for the feedback. > > > My understanding is that when you have an init.pp with import "*" in > > it, it will be able to find the rest of the manifests in the module. > > However, I was operating under the assumption that all the modules in > > the environment get auto-imported at the beginning of the run > > (otherwise how are top-level includes found). > > If you dont comply to the module naming conventions - you should - then > you have to make import statements in your site.pp or a file directly > imported by site.pp to import those files. Else the master just wont > know where to find your files. > > So if class foo is in /some/other/dir/bar.pp you need to have an import > statement that specifically hits that file. > > > > > > > > > So is there no way then to have several manifests with their own > > namespaces bound together in the same module? The alternative > > (splitting them into their own modules) makes my maintenance duties > > that much messier. Thanks. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.
