> I don't know the answer to your question, but as an alternative, I believe > you can specify more than one parentnode, so the node's entry could contain > > parentnode: 192_168_100_0 > parentnode: zzbasenode > > to inherit things from both. Hi, thnak you for your answer. But that's not the problem. I could define "parentnode: zzbasenode" in puppetc2 and "parentnode: 192_168_100_0" in zzbasnode Most entries from puppetc1, zzbasenode and 192_168_100_0 are included in the puppet catalog file 'puppetc2.zz.example.com.yaml' Only those entries, that not exist at puppetc2 are included from zzbasenode. And only those entries, that are not defined in puppetc2 and zzbasenode are included from 192_168_100_0. Thats the problem. Is is possible to define expansible attributes by parentnodes?
Example: HostEntry attruibutes are defined in puppetc1: HostEntry: 1.2.3.4:first.entry.from.hostconfig HostEntry: 2.3.4.5:second.entry.from.hostconfig and 192_168_100_0: HostEntry: 100.101.110.111:first.entry.from.zz.profile HostEntry: 200.202.220.222:second.entry.from.zz.profile but in the catalog file only the HostEntry attrbiutes from puppetc2 are visible. Other attributes from the network profile are included: defaultServerList: 192.168.100.101 followReferrals: TRUE ... defaultSearchBase: dc=zz,dc=example,dc=com Any idea? regards puppetplayer -- 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.
