hello,
----- "Luke Kanies" <[email protected]> wrote:
> On Oct 27, 2009, at 4:37 PM, Markus Roberts wrote:
>
> > > For instance, I know Volcane has mentioned that the reason he
> > > overrides environments on clients is because it's the only way he
> > > can force ordering.
> >
> > As in having proto-environments that you sequentially pass through
> > on the way to the final environment (no skipping stages!) or am I
> > missing the point here?
>
> More like "I know X has to be done before my main configuration works,
> so I put X in a special 'setup' environment and run it once".
> I.e., exactly what I desperately want to avoid and am embarrassed is
> necessary. I think fixing this is probably the real goal here.
We've often discussed 'anchor' classes on the graph.
So there might be a class beforehook and afterhook that if nothing gets done
simply ends up before and after all classes.
But if I now do:
file{"/foo":
require => Class["afterhook"]
}
or
file{"/foo":
before => Class["beforehook"]
}
I would basically ensure these things happen first or last, and if i had 10
things to happen first - configure yum, create repos, make cache - I'd just
make them all happen before beforehook.
I'd hate to imagine the hell of coding this behavior though
--
R.I.Pienaar
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Developers" 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-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
