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

2015-02-10 Thread Henrik Lindberg
On 2015-10-02 1: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 -- apache You

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

2015-02-10 Thread Walter Heck
I'm personally more of a fan of what some programming languages call interfaces; a sort of contract if you will that a module implements. So for instance olindata::galera could look for any class that implements the IMysql interface. That way, I don't really need to worry if the end-user is

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

2015-02-10 Thread Hunter Haugen
This reminds me of ARM-17 that I tried to model after Haskell/Python/Clojure https://github.com/puppetlabs/armatures/pull/64 . It stalled out due to lack of time, though it may have some relevant content. -Hunter On Tue, Feb 10, 2015 at 12:44 PM, Heck, Walter walterh...@olindata.com wrote:

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

2015-02-10 Thread Heck, Walter
Hi Trevor, On Tue, Feb 10, 2015 at 9:17 PM, Trevor Vaughan tvaug...@onyxpoint.com wrote: Walter: This would be nice, but variables are the...uh...variable here. Many people only expose the variables that they need while others expose every variable they can find. It would be an interesting

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

2015-02-10 Thread Henrik Lindberg
On 2015-10-02 21:17, Trevor Vaughan wrote: To Henrik: Yes, this make sense, it would be nice to have some easy way to keep the purely Puppet DSL portions separate though. Yeah, but that is the way it works - so way to much to change to make that happen. I guess it would be possible to have

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

2015-02-10 Thread Heck, Walter
Hi Henrik, On Tue, Feb 10, 2015 at 9:30 PM, Henrik Lindberg henrik.lindb...@cloudsmith.com wrote: On 2015-10-02 19:52, Walter Heck wrote: I'm personally more of a fan of what some programming languages call interfaces; a sort of contract if you will that a module implements. Yes that is

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

2015-02-10 Thread Trevor Vaughan
To Henrik: Yes, this make sense, it would be nice to have some easy way to keep the purely Puppet DSL portions separate though. Walter: This would be nice, but variables are the...uh...variable here. Many people only expose the variables that they need while others expose every variable they can

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

2015-02-10 Thread Henrik Lindberg
On 2015-10-02 19:52, Walter Heck wrote: I'm personally more of a fan of what some programming languages call interfaces; a sort of contract if you will that a module implements. Yes that is good - does not solve the issue of modules having the same name though - either the module name must

[Puppet-dev] Announce: Facter 2.4.1 available

2015-02-10 Thread Peter Huene
Facter 2.4.1 is a bug fix release in the Facter 2 series. Included in this release are fixes for the following bugs: - The ec2_metadata fact was not filtering out sensitive IAM security credentials. - The virtual fact's detection of KVM hypervisors when running as non-root on Linux