Puppet users - Jan 2008 - Prerequisites for almost all tasks

Hello everybody,

almost one year ago, there was a short discussion about certain
resources which are intended to happen before any other resources (see
[1] and replies).
To quickly summarize it: There may be some few tasks (like creating some
files required for installing any packet on a gentoo system, or mounting
a nfs share needed by subsequent installation/copy tasks).
Back then, the outcome was that there wasn''t any good way to solve this
issue.

Since I''m running into the same problem right now (what I need is to
install an NFS client, mount an NFS share and replace a few
configuration files before any of the subsequent
installation/configuration tasks is done). Of course, I could add a list
of "Require"d resources to all those tasks, but that''s not
quite the way
one would like to proceed; I''d rather like to have some way of marking
one class or module as a prerequisite for all the others.
Is there any way to do that?

Thanks,
	Benjamin
[1] http://mail.madstop.com/pipermail/puppet-users/2007-February/001342.html

On Jan 10, 2008 1:50 AM, Benjamin Gufler <benjamin.gufler@cs.tum.edu>
wrote:
> one would like to proceed; I''d rather like to have some way of
marking
> one class or module as a prerequisite for all the others.
> Is there any way to do that?
I believe you can do this:

resource { "name":
    require => Class["classname"],
}

David Schmitt does it in his ifupdown module.

http://git.black.co.at/?p=manifests.git;a=blob;f=modules/ifupdown/manifests/init.pp

On Jan 10, 2008, at 12:50 AM, Benjamin Gufler wrote:
> Hello everybody,
>
> almost one year ago, there was a short discussion about certain
> resources which are intended to happen before any other resources (see
> [1] and replies).
> To quickly summarize it: There may be some few tasks (like creating  
> some
> files required for installing any packet on a gentoo system, or  
> mounting
> a nfs share needed by subsequent installation/copy tasks).
> Back then, the outcome was that there wasn''t any good way to solve
> this
> issue.
>
> Since I''m running into the same problem right now (what I need is
to
> install an NFS client, mount an NFS share and replace a few
> configuration files before any of the subsequent
> installation/configuration tasks is done). Of course, I could add a  
> list
> of "Require"d resources to all those tasks, but that''s
not quite the
> way
> one would like to proceed; I''d rather like to have some way of
marking
> one class or module as a prerequisite for all the others.
> Is there any way to do that?
The closest thing to this right now is specifying a relationship to a  
class, which is equivalent to specifying a relationship to every  
resource in that class.

-- 
I have a switch in my apartment... It doesn''t do anything. Every once
in a while, I turn it on and off. One day I got a call... It was from
a woman in France... She said, "Cut it out!"
     -- Stephen Wright
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com