Re: [Puppet-dev] Thoughts on Module Namespace Conflicts

2015-02-20 Thread Wil Cooley
On Mon, Feb 9, 2015 at 4:23 PM, Trevor Vaughan wrote: > I was talking with a few folks today about potential resolutions to module > namespace issues. > > == Fundamental Issue == > > puppetlabs_apache -- Installs To --> apache > example42_apache -- Installs To --> apache > theforeman_apache -- In

Re: [Puppet-dev] Thoughts on Module Namespace Conflicts

2015-02-12 Thread Trevor Vaughan
modules: > https://github.com/puppetlabs/puppet/blob/master/lib/puppet/node/environment.rb#L233-L241 > > > On Thu Feb 12 2015 at 10:32:24 AM R.I.Pienaar wrote: > >> >> >> - Original Message - >> > From: "Dominic Cleal" >> > To: &quo

Re: [Puppet-dev] Thoughts on Module Namespace Conflicts

2015-02-12 Thread Erik Dalén
quot;Dominic Cleal" > > To: "puppet-dev" > > Sent: Thursday, February 12, 2015 10:30:21 AM > > Subject: Re: [Puppet-dev] Thoughts on Module Namespace Conflicts > > > On 11/02/15 18:13, Trevor Vaughan wrote: > >> Heh, that's probably because i

Re: [Puppet-dev] Thoughts on Module Namespace Conflicts

2015-02-12 Thread R.I.Pienaar
- Original Message - > From: "Dominic Cleal" > To: "puppet-dev" > Sent: Thursday, February 12, 2015 10:30:21 AM > Subject: Re: [Puppet-dev] Thoughts on Module Namespace Conflicts > On 11/02/15 18:13, Trevor Vaughan wrote: >> Heh, that's p

Re: [Puppet-dev] Thoughts on Module Namespace Conflicts

2015-02-12 Thread Dominic Cleal
On 11/02/15 18:13, Trevor Vaughan wrote: > Heh, that's probably because it's the third hit in the list when you > search for Apache on the Forge. > > Is there a way for people to mark Forge modules as unmaintained? Not as far as I know. I ought to upload a new release with a big warning in the R

Re: [Puppet-dev] Thoughts on Module Namespace Conflicts

2015-02-11 Thread Trevor Vaughan
r10k definitely helps with this but you still have to maintain the configurations for each of your environments. So, 50 hosts with one different/conflicting module each == 50 branches with one line different in a file. (yeah, straw man). Also, you still can't mix and match your conflicting namespa

Re: [Puppet-dev] Thoughts on Module Namespace Conflicts

2015-02-11 Thread Felix Frank
On 02/10/2015 01:23 AM, Trevor Vaughan wrote: > 2) You have to create a separate environment for each host group > (potentially each host) that you want to have use the differing code. > >* Issue: This is a LOT of overhead for a couple of modules and may > have other ramifications in terms of p

Re: [Puppet-dev] Thoughts on Module Namespace Conflicts

2015-02-11 Thread Trevor Vaughan
Heh, that's probably because it's the third hit in the list when you search for Apache on the Forge. Is there a way for people to mark Forge modules as unmaintained? Trevor On Wed, Feb 11, 2015 at 5:24 AM, Dominic Cleal wrote: > On 10/02/15 00:23, Trevor Vaughan wrote: > > I was talking with a

Re: [Puppet-dev] Thoughts on Module Namespace Conflicts

2015-02-11 Thread Dominic Cleal
On 10/02/15 00:23, Trevor Vaughan wrote: > I was talking with a few folks today about potential resolutions to > module namespace issues. > > == Fundamental Issue == > > puppetlabs_apache -- Installs To --> apache > example42_apache -- Installs To --> apache > theforeman_apache -- Installs To -->

[Puppet-dev] Thoughts on Module Namespace Conflicts

2015-02-09 Thread Trevor Vaughan
I was talking with a few folks today about potential resolutions to module namespace issues. == Fundamental Issue == puppetlabs_apache -- Installs To --> apache example42_apache -- Installs To --> apache theforeman_apache -- Installs To --> apache You get my point... == Current Solutions == Ri