On Monday, July 14, 2014 8:55:38 AM UTC-5, Kristof Willaert wrote: > > [snip] > > You will not be able to collect that resource on the node that exports it >> (you would again -- and rightfully -- get a duplicate resource complaint), >> but I think otherwise you should be ok. >> > > The documentation for exported resources suggests otherwise: > > Any node (including the node that exported it) can then *collect* the > exported resource and manage its own copy of it. [1] > > I must say I haven't tried it myself, but unless I misinterpret the > sentence above, it should be possible. >
You're not misinterpreting the docs, but you *are* misinterpreting my statement. Although *generally* the node exporting a resource can collect that resource, if the OP used the approach I described then his nodes would not be able to collect the Site::Secondary_host resources they declare themselves. If they tried to collect their own, then it would yield a duplicate Host resource (from the defined type body; because he already, separately, declares a Host for the node itself). The key there is that -- I think -- the type's body will not be evaluated by the declaring node for instances that it does not collect, even those that it declares itself. John -- 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/e05c726c-b0ca-40be-8f5a-a38df765a9cf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
