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
Guess I should have read to point 6 in PUP-1434, init.pp is special. Got
it, thanks a bunch.
Jon
On Tuesday, 28 August 2018 10:08:16 UTC-6, j...@jnjschneider.com wrote:
>
> So does this mean if the path is '$module_path/seed/manifests/init.pp' then
> the define name will now need to be
So does this mean if the path is '$module_path/seed/manifests/init.pp' then
the define name will now need to be 'seed::init::remote_file' in place of
'remote_file'?
Thanks,
Jon
On Tuesday, 28 August 2018 09:50:48 UTC-6, Branan Purvine-Riley wrote:
>
> Hi Jon,
>
> In Puppet 6 we're going to
Hi Jon,
In Puppet 6 we're going to start requiring that the names of
classes/defines match the name that's implied by their file path[1]. We
added that deprecation warning in 5.5.6[2] as part of a push to get
upcoming Puppet 6 changes printing warnings whenever possible.
[1]
I was away on vacation for a month, upon getting back I am finding the
Puppet Agent is now throwing a warning on all of the defines I have in a
module that is applied to all our Linux servers. (we are auto updating
point releases)
Warning: Unacceptable location. The name 'remote_file' is
