Hi,
[snip]
But the problem is that a certain module I include follows the principles of
> Example42 's Puppet modules of splitting up resources in classes according
> to the operating system.
>
[snip]
> When I include this specific class in my developer-workstation module
> below, the resource chaining doesn't work anymore..
>
This smells like bug 8040. The ordering of the resources is not transferred
to the included classes.
It is possible to work around this problem by declaring dummy resources in
the composite class that mark
the start and end of the class. The guys from puppetlabs use a custom
"anchor" type, but something
like a notify seems to work just as well.
In the composite class:
class composite {
notify { "Start of class composite": message => "Start of class
composite" }
notify { "End of class composite": message => "End of class composite"
}
...
}
Then in the subclasses, use:
class composite::sub1 {
...
Notify["Start of class composite"] -> Class["composite::sub1"] ->
Notify["End of class composite"]
}
It all looks a bit verbose to me, but as mentioned in bug 8040, this will be
fixed in core.
Kind regards,
kristof
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
