On Nov 16, 2010, at 12:15 PM, Russell Jackson <r...@csub.edu> wrote: > I stand corrected. It does work. > > I've always thought of defines as macros, but apparently they are objects > themselves. I'm still confused why they don't appear in my catalogs. Would > nesting them inside of classes have anything to do with that?
What actually happens in the catalog is that a relationship is established with every resource in the collection created by the defined resource type. The trend seems to be moving in the direction of making defined resource types more like native types in the catalog, but I don't have easy access to the tickets on my phone. The same thing happens when establishing a relationship to a class. In the catalog this is actually a relationship to all resources in the collection of resources created by the class. Hope this helps, -Jeff -- 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.
