Jira (PUP-7541) Explore removing export / collect / virtual / realize syntax

[Hunter (Hunner) Haugen (JIRA)]

Title: Message Title

Hunter (Hunner) Haugen commented on PUP-7541   Re: Explore removing export / collect / virtual / realize syntax I have not read the entire conversation yet (longthread is long) but generally agree with Sean Millichamp's major points. I also want to offer a few technical details. <||> collectors are often used to add resource dependencies when we are unsure of any/all of the declared resources. Similar to the autorequire et al in native types. The biggest example that comes to mind is https://github.com/puppetlabs/puppetlabs-tomcat/blob/1.7.0/manifests/instance/dependencies.pp as there can be an arbitrary number of tomcat instances with widely varying paths and many (or none) defined types using the various instances. Building out such a tree was not possible without collecting on a commonly-shared quality (that of the catalina_base or catalina_home values). From a module dev perspective, we cannot depend on the existence of the puppetdb service. We also cannot depend on the ability to export resources, though may offer solutions that can take advantage of such (eg https://github.com/puppetlabs/puppetlabs-haproxy/blob/1.5.0/manifests/backend.pp#L66). I don't think module devs care about virtual resources; they are too entangled with the collector realization and spaghetti-code anti-patterns that we just avoid them. Add Comment   This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.