I have been backed into a corner, by they way puppet works, but some third 
party module.

Basically I have two resources defined:

a {$somevar:}
b::b {$somrvar:}

both have code that looks something like this:
    if (!defined(File[$name])) {
        file { $name:
...
    }

According to the documentation 'defined' is dependent on parse order.  So 
resource definition 'a' should be parsed first and win.  But it doesn't, no 
matter how I order 'a' and 'b::b', resource definition 'b::b' always 
defines the file.  I even tried puppet version 3.1.1.  Same problem.  My 
problem is that resource "b::b" does it horribly wrong.  It causes the 
runtime of my manifest to balloon out from 2mins to over 10 minutes.  It 
uses the wrong group.  That would be okay if I could just put 'a' first and 
have 'b::b' go silent.

Does anyone know why this is happening?  How is "b::b" being parsed first 
even though "a" is ahead in the file?

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to