On 11/16/2010 11:33 AM, Nan Liu wrote:
On Tue, Nov 16, 2010 at 11:21 AM, Yushu Yao<y...@lbl.gov> wrote:
Hi Experts,
I am in a situation that need one definition to require another (to enforce
execution order). E.g.
define a(x,y,z) {
do task 1
}
define b(u,v,w) {
so task 2
}
To use them:
Below won't make sure task 1 is executed before task 2 (or does it?):
The question is:
Won't it help if Puppet support require=>Definition["inst_a"] directly?
Yes it supports it.
a { inst_a:
x=>"x", ...
}
b { inst_b:
u=>"u", ...
require=>A["inst_a"],
}
Just capitalize the first letter:
define foo:bar ...
require => Foo:Bar[".."]
I stand corrected. It does work.
I've always thought of defines as macros, but apparently they are
objects themselves. I'm still confused why they don't appear in my
catalogs. Would nesting them inside of classes have anything to do with
that?
--
Russell A Jackson <r...@csub.edu>
Network Analyst
California State University, Bakersfield
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-us...@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.
