>
> That's awfully surprising if those data appear in an Hiera data file from 
> which you are successfully loading other data.  If that is in fact 
> happening then the most likely reason would be that a resource-like class 
> declaration for that class somewhere in your manifest set is explicitly 
> declaring different parameter values for that class (in which case the 
> Hiera data will not be consulted).  But if that were the case, then I would 
> expect Puppet to raise an error when you added your own resource-like 
> declaration of the same class.  Another possibility is that there are 
> conflicting data in some higher-priority level of your data hierarchy, but 
> that would be surprising considering how you arrived where you now are.
>
> My best guess, therefore, is that the file in which you placed the 
> parameter data is not being consulted at all for the node in question (so 
> that in fact you are *not* successfully loading other data from it, 
> either).
>
>
I'm testing with a minimal setup, just to make sure.

I have one manifest, site.pp, that I call locally (no server), and one 
hiera file, common.yaml.

I found it.  I stupidly commented the whole class declaration in site.pp.

When I leave just the class declaration it works:

class {'postgresql::server::contrib':
}


Is there a way to have the class declaration in hiera? I tried using this 
at the top of my yaml file but it didn't work:

---
classes:
  - postgresql::server::contrib
 

>  
>
>> So class parameters are automatically looked up in hiera, but define 
>> parameters (or whatever name it is for objects) is not?
>>
>
>
> That is correct.  There are good reasons for it, but a discussion of those 
> would be tangential.  If you're interested, you can find at least one such 
> discussion in the archives of this group.
>
>  
Ok thanks,

Are the modules supposed to manage that or the user? 

Thanks,

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/b50f0abe-bf50-453e-913c-9baac7802d20%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to