[Puppet-dev] Ephemeral resources

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

Re: [Puppet-dev] Ephemeral Resources

On Fri, Dec 9, 2016 at 5:45 PM, Trevor Vaughan wrote: > This makes sense but it *is* compile order dependent though. Therefore care > has to be taken in ensuring that all shared_data are available prior to full > resource realization in the catalog. > > This is why the

Re: [Puppet-dev] Ephemeral Resources

This makes sense but it *is* compile order dependent though. Therefore care has to be taken in ensuring that all shared_data are available prior to full resource realization in the catalog. This is why the ordering relationship matters, not for any client side reason. Basically, it would mean

Re: [Puppet-dev] Ephemeral Resources

> On Dec 8, 2016, at 11:50 AM, Trevor Vaughan wrote: > > That would work, but I'm guessing that we're going to want to be able to > access this information across resources. > > We can presently do this in the catalog as long as you time it properly. A little bit of a

Re: [Puppet-dev] Ephemeral Resources

That would work, but I'm guessing that we're going to want to be able to access this information across resources. We can presently do this in the catalog as long as you time it properly. Also, doing anything that looks more "programmish" is going to scare new users. But +1, that's basically

Re: [Puppet-dev] Ephemeral Resources

So, in theory, ephemeral resources would only have relationships on items that need them for data and/or building purposes. We already have this problem and, as more items start getting managed, we're going to run into more issues with large catalog compile and application death. I guess they

Re: [Puppet-dev] Ephemeral Resources

On Wed, 7 Dec 2016 at 14:54 Trevor Vaughan wrote: > I was looking through the puppetlabs-concat module as well as some of my > modules that have aggregation functionality and I realized that the catalog > really shouldn't be sending the intermediary resources to the

[Puppet-dev] Ephemeral Resources

I was looking through the puppetlabs-concat module as well as some of my modules that have aggregation functionality and I realized that the catalog really shouldn't be sending the intermediary resources to the client. While I'm not positive, the ability to mark resources as ephemeral *might* go