How difficult would it be to create a third type of resource which is an 'ephemeral resource' whose only purpose is data collection on a host to be used by some other collector?
These items would not be part of the catalog or added to the graph but would instead just hang around for reference during compilation. This would fix the catalog explosion issue when you start doing exported resources based on large numbers of things and/or things like firewall rules and copious file_line resources. Basically, a 'data' -> 'collector' pattern where you can optimize...well...everything into a MUCH smaller catalog that is sent to the client for processing. Thanks, Trevor -- Trevor Vaughan Vice President, Onyx Point, Inc (410) 541-6699 x788 -- This account not approved for unencrypted proprietary information -- -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/CANs%2BFoW-%2BoXpHzxyQrZOEwp9JSdH9kDV4aPLtngNzo_Rtqk4DQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
