[Puppet-dev] Announce: Puppet 3.3.1-rc1 Available

**Release candidate:** Puppet 3.3.1 has not yet been released; it entered its first release candidate on September 23, 2013. 3.3.1 is to be a bug fix release in the Puppet 3.3 series. The focus of the release is fixing backwards compatibility regressions that slipped in via the YAML deprecations

Re: [Puppet-dev] Announcing pull requests metrics

On Mon, Sep 23, 2013 at 1:36 PM, William Van Hevelingen wrote: > Can you add the openstack modules as well? They're under the stackforge > namespace on github and puppetlabs namespace on the forge. There are twelve > of them. > Hey Will, those metrics are intended for our team to keep tabs on the

Re: [Puppet-dev] Release branches for puppetlabs modules

On 23.09.2013 16:17, William Van Hevelingen wrote: Hi All, ashp mentioned in #puppet that puppetlabs has not come to a decision on doing branches per major versions yet. This email is to help start a public discussion. The primary use case that Im interested in is the Openstack modules as the

Re: [Puppet-dev] Idea around warnings and containment

On Sunday, September 22, 2013 5:22:10 PM UTC-5, Luke Kanies wrote: > > > On Sep 19, 2013, at 11:35 AM, John Bollinger > > > wrote: > > On Tuesday, September 17, 2013 1:36:34 PM UTC-5, Luke Kanies wrote: > > If I'm right, then the choices are: >> >> * Rather than risk warning people about things

Re: [Puppet-dev] Announcing pull requests metrics

William, Emma has returned to school. I'll mention the request to Ryan Coleman, Forge Product Owner. Thanks, Jeff On Mon, Sep 23, 2013 at 1:36 PM, William Van Hevelingen wrote: > Awesome! > > Emma, > > Can you add the openstack modules as well? They're under the stackforge > namespace on gith

Re: [Puppet-dev] Announcing pull requests metrics

Awesome! Emma, Can you add the openstack modules as well? They're under the stackforge namespace on github and puppetlabs namespace on the forge. There are twelve of them. On Mon, Sep 23, 2013 at 1:23 PM, Jeff Weiss wrote: > William, > > Yes, http://forge-module-metrics.herokuapp.com. The work

Re: [Puppet-dev] Announcing pull requests metrics

William, Yes, http://forge-module-metrics.herokuapp.com. The work that Hailee had done was adapted by another of our summer interns, Emma. How's that for response time? :) -Jeff On Mon, Sep 23, 2013 at 1:19 PM, William Van Hevelingen wrote: > Can we get a similar setup for the major puppetlab

Re: [Puppet-dev] Announcing pull requests metrics

Can we get a similar setup for the major puppetlabs modules too like apache, mysql, postgresql, concat, inifile, rabbitmq, ntp, etc ? :) Looks great, William On Mon, Sep 23, 2013 at 1:14 PM, Dustin J. Mitchell wrote: > That is neat, and shows some interesting trends, particularly the > large sp

[Puppet-dev] Release branches for puppetlabs modules

Hi All, ashp mentioned in #puppet that puppetlabs has not come to a decision on doing branches per major versions yet. This email is to help start a public discussion. The primary use case that I'm interested in is the Openstack modules as they rely heavily on the puppetlabs modules like apache,

Re: [Puppet-dev] Announcing pull requests metrics

That is neat, and shows some interesting trends, particularly the large spike in pull request lifetime around March, and the subsequent drawdown. Clicking on merged/closed the pie chart, it looks like most of those were closed, so I assume that was a backlog of stale pull requests that the new sys

Re: [Puppet-dev] Re: an undef epiphany for puppet 4

This is quite valuable. I tend to use "" (the empty string) for this and check against that in my logic. It would be much cleaner to just be able to set something to undef and have it "do the right thing". Trevor On Mon, Sep 23, 2013 at 1:31 PM, Henrik Lindberg < henrik.lindb...@cloudsmith.com

[Puppet-dev] Module team update: 2013-09-04 - 2013-09-23

I am terrible at getting these out on schedule. Another busy month with a whole bunch of stuff going on, internally and externally. The main highlights of the month are the recently rewritten puppetlabs-mysql and puppetlabs-postgresql modules. Both have had huge overhauls internally and are now

Re: [Puppet-dev] Plugin sync support for external facts

Andy, thanks for getting the brainstorm going. I've attempted to address each item below. On Monday, September 23, 2013 11:38:25 AM UTC-5, Andy Parker wrote: > > On Sat, Sep 21, 2013 at 1:00 PM, John Julien > > > wrote: > >> I'd like to start some discussion around how to implement >> https:

[Puppet-dev] Re: an undef epiphany for puppet 4

On 2013-23-09 15:38, Andy Parker wrote: On Tue, Sep 17, 2013 at 10:13 AM, Henrik Lindberg mailto:henrik.lindb...@cloudsmith.com>> wrote: On 2013-17-09 18:55, Andy Parker wrote: On Tue, Sep 17, 2013 at 9:35 AM, Henrik Lindberg mailto:henrik.lindb...@cloudsmith.com>

Re: [Puppet-dev] Plugin sync support for external facts

On Sat, Sep 21, 2013 at 1:00 PM, John Julien wrote: > I'd like to start some discussion around how to implement > https://projects.puppetlabs.com/issues/9546 (Plugin sync support for > external facts) > > Since external facts can be any type of executable and additionally > straight json and yaml

Re: [Puppet-dev] Plugin sync support for external facts

On Mon, Sep 23, 2013 at 9:37 AM, Eric Sorenson wrote: > On Sep 23, 2013, at 2:29 AM, Andy Parker wrote: > > > I guess my first question is, what scenarios do we need to support that > aren't handled right now (or handled in a very clumsy way)? > > Facter/puppet when run as non-root users need t

Re: [Puppet-dev] Plugin sync support for external facts

On Sep 23, 2013, at 2:29 AM, Andy Parker wrote: > I guess my first question is, what scenarios do we need to support that > aren't handled right now (or handled in a very clumsy way)? Facter/puppet when run as non-root users need to run external facts if they are defined, but currently they o

[Puppet-dev] Announcing pull requests metrics

It is my pleasure to present our new pull requests metrics app ( http://pullrequestmetrics.herokuapp.com/), courtesy of Hailee. Hailee was one of this years interns, and she was tasked with creating a dashboard for the pull request metrics across our different projects. She did an excellent job of

[Puppet-dev] Puppet Dev Community Summary (2013-09-23)

As of last week most our backlogged pull requests have been cleared up; you should be able to expect faster turnaround on new pull requests. Puppet Dev Community Summary - Finished Card Total: *26* vs 18 last week - Merged: 18 vs 12 last week - Not Merged: 8 vs 5 last week Please see th

Re: [Puppet-dev] Plugin sync support for external facts

On Mon, Sep 23, 2013 at 7:56 AM, John Julien wrote: > On Monday, September 23, 2013 4:29:35 AM UTC-5, Andy Parker wrote: > >> On Sat, Sep 21, 2013 at 1:00 PM, John Julien wrote: >> >>> I'd like to start some discussion around how to implement >>> https://projects.puppetlabs.**com/issues/9546

Re: [Puppet-dev] Plugin sync support for external facts

On Monday, September 23, 2013 4:29:35 AM UTC-5, Andy Parker wrote: > > On Sat, Sep 21, 2013 at 1:00 PM, John Julien > > > wrote: > >> I'd like to start some discussion around how to implement >> https://projects.puppetlabs.com/issues/9546 (Plugin sync support for >> external facts) >> >> > Th

Re: [Puppet-dev] Re: an undef epiphany for puppet 4

On Tue, Sep 17, 2013 at 10:13 AM, Henrik Lindberg < henrik.lindb...@cloudsmith.com> wrote: > On 2013-17-09 18:55, Andy Parker wrote: > >> On Tue, Sep 17, 2013 at 9:35 AM, Henrik Lindberg >> > henrik.lindberg@**cloudsmith.com >> >> >> wrote: >> >> On 2013-17-09 5:44, Henrik Lindberg wrote: >> >

Re: [Puppet-dev] Plugin sync support for external facts

On Sat, Sep 21, 2013 at 1:00 PM, John Julien wrote: > I'd like to start some discussion around how to implement > https://projects.puppetlabs.com/issues/9546 (Plugin sync support for > external facts) > > That issue unfortunately only states that it should do it, but nothing about why we should d