On Oct 27, 12:35 pm, Luke Kanies <[EMAIL PROTECTED]> wrote:
> The entire set of manifests is evaluated on the server, producing a
> catalog which is evaluated on the client.
Ok, so the puppetmaster creates a static catalog (devoid of variables
and control structures) for any resources applicable to the given
client so it can apply them. Which in the case of the svn_repo
example in the documentation on definitions, means that by the time
the client gets the catalog, it just sees an 'exec' that either does
or doesn't have the require attribute.
> Thus, you never have to worry about ordering between language
> constructs like 'if' and catalog resources, because the language
> constructs are *always* evaluated before any resources are
> evaluated.
That answers part of my question about whether the "non-
resource" (obviously more appropriately titled "language") bits of the
manifests are evaluated before the resources. But I'm not sure it
answered the the other question regarding the order of evaluation of
the language constructs performed on the puppetmaster. So in the case
of:
if $foo { $baz = "quux" }
$foo = "bar"
...does the puppetmaster care in which order these types of language
constructs exist in the given resource? Or does it handle the
assignments before any control structures are evaluated?
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
