On Thu, Apr 26, 2018 at 7:42 PM, Trevor Vaughan
wrote:
> Oh, and you're possibly setting yourself up for SERVER-94 hell if you're
> not EXTREMELY careful.
>
Yep, I'm aware of the issues with environment isolation, as I filed the
initial redmine ticket more than 5 years ago describing the problem
On Thu, Apr 26, 2018 at 7:42 PM, Trevor Vaughan
wrote:
> I would ask that you only vendor items that are super generic and that you
> namespace them such that they won't interfere with people already written
> codebases.
>
For modules that were previously in core puppet, we are plan on appending
On Mon, Apr 23, 2018 at 6:44 PM, Eric Sorenson wrote:
> Hi all, we've started landing changes for what will become Puppet Platform 6.
> Here's the News You Can Use relating to the release.
Hello Eric,
I've noticed that mcollective has been removed of the puppet-agent package.
Would it be possi
Oh, and you're possibly setting yourself up for SERVER-94 hell if you're
not EXTREMELY careful.
On Thu, Apr 26, 2018 at 10:42 PM, Trevor Vaughan
wrote:
> I would ask that you only vendor items that are super generic and that you
> namespace them such that they won't interfere with people already
I would ask that you only vendor items that are super generic and that you
namespace them such that they won't interfere with people already written
codebases.
The following seem relatively safe since they've been in use for quite some
time:
- stdlib
- archive (maybe)
- inifile
- pow
Some people raised concerns about vendoring modules in the puppet-agent
package[1]. I wanted to provide some more context about the "why", and some
refinements to the "how".
First, new users should be able to download the puppet-agent package and
manage basic resources for the platform they're run
