-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> It seems that now the recommendation is to have one file per
> class?
Yes it is.
> If no, where puppet will look for foo::a::b class, (aside from
> module/foo/manifest/a/b.pp)?
But you can also have this class in
module/foo/manifest/a.pp
module
- Original Message -
> From: "DEGREMONT Aurelien"
> To: puppet-dev@googlegroups.com
> Cc: "Peter Meier"
> Sent: Wednesday, October 23, 2013 3:44:55 PM
> Subject: Re: [Puppet-dev] #8433 Globbing imports are now considered undefined
> behavior
>
> Thanks a lot.
> This was exactly what I
Thanks a lot.
This was exactly what I was looking for.
It seems that now the recommendation is to have one file per class?
If no, where puppet will look for foo::a::b class, (aside from
module/foo/manifest/a/b.pp)?
Aurélien
Le 23/10/2013 16:29, Peter Meier a écrit :
-BEGIN PGP SIGNED M
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> I'm trying to find an official document explaining how classes
> should be organized.
This should probably help you:
http://docs.puppetlabs.com/puppet/latest/reference/lang_namespaces.html
~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.15
Hi all
I'm currently working on upgrading our old 0.25 puppet infrasctructure
to something more up to date.
I've just faced the issue detailled in:
https://projects.puppetlabs.com/issues/8433
Regarding automatic import and import "*.pp" behavior change.
I'm trying to find an official documen
