Yup, I hear ya. This was a pain until I realized that the only
variables defined in nodes are inherited from node to node. The
variables defined in classes that are included by the node must be
expressed using the variable's full context. I just ended up mapping
certain variables to other variables in my server templates and it
seems to work fine. Modules will invariably use different variable
names for the same information so it seems like this kind of duct tape
is unavoidable.
--steev
tel: (612) 840-6253
On Jun 27, 2010, at 1:39 PM, Douglas Garstang
<doug.garst...@gmail.com> wrote:
> On Sun, Jun 27, 2010 at 11:28 AM, Steve Neuharth
> <steve.neuha...@gmail.com> wrote:
>> I think you could do:
>>
>> node 'node1.fr.xxx.com' {
>> include facility::sjc
>> $my_ldap_server = $facility::sjc::ldap_server
>> include ldap::client
>> }
>
> That seems to work. Not pretty though. I'll go see if it causes any
> other problems, apart from rubbing my logical brain the wrong way.
> Thanks.
>
> Doug.
>
> --
> 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
> .
>
--
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.
