On Thursday, November 21, 2013 10:29:37 AM UTC-6, Bret Wortman wrote: > > Wait -- so this collects every occurrence thoughout the database, not just > for the system being processed? >
Yes, that's the point of exported resources. They allow resources the catalog compilation process for one node's catalog to emit resource declarations that are available for incorporation into ANY node's catalog. It only makes sense to do this with resources that are in some way specific to the exporting node. The canonical example is Host resources -- if each node exports a Host resource describing itself and collects all the exported Hosts, then all managed nodes will end up with /etc/hosts files listing (at least) all managed nodes. > I think the word "node" was tripping me up in the online documentation -- > I was reading "node" and thinking "resource". Okay, I get it now, and > you're absolutely right -- this is a terrible use of exported resources. I > think what I was looking for was virtual, not exported, resources. > > No, I think you were just looking for collections. You can use them with ordinary (non-virtual) resources. If you are not already using virtual resources to manage the Yum repos then I don't see what advantage you would obtain by converting your ordinary resources to virtual ones. 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/8f851721-c4f2-44e8-97ad-5e68afd8581d%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
