-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello Devon,
You're tight and that's the point I was looking for.
I discovered that point when doing some tests after Andrew's contribution.
So, now it works and I'll be able to deal with class ordering.
Thanks for your answer,
JB
On 31/10/2011 18:45, devon wrote:
>> And for classes definition, I got: class pkgrepo {
>> Nginx::Vhost["packages.iscoolapp.com"] -> Class['Pkgrepo'] include
>> pkgrepo::install,pkgrepo::config
>>
>> }
>
> The way I understand it, all "included" classes are basically
> included at the same time before catalog compilation. And then the
> resource dependencies don't take effect until the catalog is being
> applied to the node...or in short - "includes" aren't treated like
> resources.
>
> You basically end up with a node that includes pkgrepo,
> pkgrepo::install, and pkgrepo::config classes, then puppet ensures
> that Nginx::Vhost["packages.iscoolapp.com"] occurs before
> Class["pkgrepo"] - ignoring any sort of ordering for classes that
> pkgrepo included.
>
> To ensure the strict ordering when classes include other classes,
> you need to specify the requirements for all the classes - something
> like this should work:
>
>
> class pkgrepo { Nginx::Vhost["packages.iscoolapp.com"] ->
> Class['pkgrepo::install'] -> Class['pkgrepo::config'] ->
> Class['pkgrepo'] include pkgrepo::install,pkgrepo::config }
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk6u6IMACgkQM2eZoKJfKd3SwwCgi5nukmVgCL8FtbF6AVq5btbO
pRYAoITEGc4mzjAAMtYtxtE3hKKKAnjt
=1dAq
-----END PGP SIGNATURE-----
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
