Hi John,
Would you have any idea why this would fail
file
#puppet parser validate adhoc.pp
Warning: Unacceptable location. The name 'adhoc' is unacceptable in file
'/opt/puppetlabs/puppet/modules/adhoc/manifests/adhoc.pp' (file:
/opt/puppetlabs/puppet/modules/adhoc/manifests/adhoc.pp, line: 1, column: 1)
adhoc.pp file:
class adhoc {
}
I put the file under
/opt/puppetlabs/puppet/modules/adhoc/manifests
this is running puppet 5.5 on a new install
Thanks,
Leo
On Wednesday, August 29, 2018 at 9:58:32 AM UTC-4, Henrik Lindberg wrote:
>
> On 2018-08-29 15:11, jcbollinger wrote:
> >
> >
> > On Tuesday, August 28, 2018 at 12:13:15 PM UTC-5, [email protected]
> > 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.
> >
> >
>
> Not quite - what is now starting to be enforced is that definitions
> must be made in a file that is on an accepted path for that definition.
>
> Best,
> - henrik
>
> > 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 [email protected] <javascript:>
> > <mailto:[email protected] <javascript:>>.
> > To view this discussion on the web visit
> >
> https://groups.google.com/d/msgid/puppet-users/916271cc-6a49-4374-afe2-d6fe0dff297d%40googlegroups.com
>
> > <
> https://groups.google.com/d/msgid/puppet-users/916271cc-6a49-4374-afe2-d6fe0dff297d%40googlegroups.com?utm_medium=email&utm_source=footer>.
>
>
> > For more options, visit https://groups.google.com/d/optout.
>
>
> --
>
> Visit my Blog "Puppet on the Edge"
> http://puppet-on-the-edge.blogspot.se/
>
>
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/dc9b55e8-f5c3-4622-a223-0d5df43e36db%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
