Le 24/10/2013 21:05, John Bollinger a écrit :
At present, if the autoloader looks for my_module::foo::bar in
my_module/manifests/foo.pp then I don't think it matters whether class
my_module::foo::bar is expressed in nested or unnested form.
I could not reproduce this behaviour with 2.6
I mea
On Tue, Oct 29, 2013 at 12:11 PM, John Bollinger
wrote:
>
>
> On Tuesday, October 29, 2013 11:05:39 AM UTC-5, Aurélien Degrémont wrote:
>>
>> Le 24/10/2013 21:05, John Bollinger a écrit :
>>
>
> [...]
>
>
>>
>>
>> I think the undocumented behavior Aurélien was concerned about is the
>> autoloader
On Tuesday, October 29, 2013 11:05:39 AM UTC-5, Aurélien Degrémont wrote:
>
> Le 24/10/2013 21:05, John Bollinger a écrit :
>
[...]
>
>
> I think the undocumented behavior Aurélien was concerned about is the
> autoloader falling back from my_module/manifests/a/b.pp to
> my_module/manifes
Le 24/10/2013 21:05, John Bollinger a écrit :
On Thursday, October 24, 2013 10:39:22 AM UTC-5, Adrien Thebo wrote:
On Thu, Oct 24, 2013 at 12:54 AM, DEGREMONT Aurelien
> wrote:
Le 23/10/2013 17:41, Peter Meier a écrit :
-BEGIN PGP SIGNED MESSAGE-
On Thursday, October 24, 2013 10:39:22 AM UTC-5, Adrien Thebo wrote:
>
> On Thu, Oct 24, 2013 at 12:54 AM, DEGREMONT Aurelien
>
> > wrote:
>
>> Le 23/10/2013 17:41, Peter Meier a écrit :
>>
>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA1
>>>
>>> It seems that now the recommendation is to
On Thu, Oct 24, 2013 at 12:54 AM, DEGREMONT Aurelien <
aurelien.degrem...@cea.fr> wrote:
> Le 23/10/2013 17:41, Peter Meier a écrit :
>
> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> It seems that now the recommendation is to have one file per
>>> class?
>>>
>> Yes it is.
>>
> :/
> Mod
Le 23/10/2013 17:41, Peter Meier a écrit :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It seems that now the recommendation is to have one file per
class?
Yes it is.
:/
Module manifests will be much more complex with a lot of files in it.
If no, where puppet will look for foo::a::b class,
-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 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
12 matches
Mail list logo
