On Tuesday, August 28, 2018 at 12:13:15 PM UTC-5, kris.b...@puppet.com wrote: > > > Hi Jon, > > As you have read, this is part of our work implementing errors to enforce > the standards set down in PUP-1434. In particular, your example > '$module_path/seed/manifests/init.pp' > looks like it is in the init file of module 'seed'. Assuming that is what > you meant, anything starting with 'seed' would be OK in that file, e.g. > 'seed', 'seed::remote_file', 'seed::foo::remote_file' would all work. Note > that as part of point 4. of PUP-1434 (now being implemented in the work of > PUP-9020), you will also not be allowed to put things like resources in the > top level, but instead should include your resources in a class, define, > function, or type declaration. >
As a matter of style, the usual recommendation is that furthermore, every class and defined type definition be located in its own file <https://puppet.com/docs/puppet/5.5/style_guide.html#separate-files>, named as predicted from its fully-qualified name. Of course, this is coupled with assigning an appropriate fully-qualified name. It is important to understand that class and type names in Puppet are independent of the pathnames of the files in which the class and type definitions appear. The importance of the pathnames is limited to enabling Puppet to *find* type and class definitions at runtime. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/916271cc-6a49-4374-afe2-d6fe0dff297d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
