[Puppet-dev] Re: Ephemeral Resources

2016-12-07 Thread John Bollinger
On Wednesday, December 7, 2016 at 7:54:44 AM UTC-6, 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 cl

Re: [Puppet-dev] Rethinking Collections

2016-12-07 Thread Eric Sorenson
On Dec 5, 2016, at 2:11 PM, Trevor Vaughan wrote: > Hi Eric, > > Unfortunately, you've now built a distribution (a very minor distribution, > but one nonetheless). As such, I would *highly* recommend following the time > honored (and massively tedious) method of having something like collecti

Re: [Puppet-dev] Rethinking Collections

2016-12-07 Thread Eric Sorenson
The bare minimum is to not 'ensure => latest' on production systems across against a repo you don't maintain. I've seen two patterns to implement this - assuming you are managing puppet components via puppet itself, obviously: 1. use the upstream repos but 'ensure' to known-good versions. Test n

[Puppet-dev] Ephemeral Resources

2016-12-07 Thread Trevor Vaughan
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 a