On 10/07/2014 04:05 AM, Britt Gresham wrote:
I think we should do 2a because there should be rough parity between
the configuration files and the command line arguments. We should
do 2 or 2a because as John says, Puppet should, Stop getting in my
way!
I think that option
On Tue, Oct 7, 2014 at 1:48 AM, Felix Frank felix.fr...@alumni.tu-berlin.de
wrote:
On 10/07/2014 04:05 AM, Britt Gresham wrote:
I think we should do 2a because there should be rough parity between
the configuration files and the command line arguments. We should
do 2 or 2a
We're excited to announce the release of Puppet Strings 0.1.0! This is a
preliminary release of the new documentation module. Our goal is to get it
into the hands of users so that we can get feedback on what direction we
should take this. The long-term goal is to have this tool eventually
replace
On Monday, October 6, 2014 5:13:43 PM UTC-5, Andy Parker wrote:
Sorry to resurrect an old thread, but this came to my attention again
today.
On Fri, Mar 14, 2014 at 6:20 AM, John Bollinger john.bo...@stjude.org
javascript: wrote:
On Thursday, March 13, 2014 8:50:19 AM UTC-5, Trevor
I'm still a fan of separate types.
Just put a nail in the coffin once and for all since this is really the
only type which tries to get fancy.
Trevor
On Tue, Oct 7, 2014 at 3:27 PM, John Bollinger john.bollin...@stjude.org
wrote:
On Monday, October 6, 2014 5:13:43 PM UTC-5, Andy Parker
First, congratulations this is awesome and will make a lot of people very
happy!
Second, typo in the README: puppet strings serever, that's one 'e' too many.
Third, is there an example module annotated with yard-style documentation
to give a people an idea of how to get this going? Some
Separate types undoes basically what package now tries to make as
transparent as possible. I guess a case could be made to have package
only deal with the OS native package provider and have separate types and
providers for secondary packages like gem, wheel/egg/whatever etc.
On Tuesday, 7
Hi list,
During the contributors summit preceding Puppetconf 2014 an effort was
started to remove Nagios from Puppet core. This effort is currently tracked
in https://github.com/puppetlabs/puppet/pull/3165 and and PUP-1077.
I'm going to jump the gun a bit here but once this lands we have a few
On Tue, Oct 7, 2014 at 7:06 PM, Daniele Sluijters
daniele.sluijt...@gmail.com wrote:
First, congratulations this is awesome and will make a lot of people very
happy!
Thanks, that's great to hear!
Second, typo in the README: puppet strings serever, that's one 'e' too
many.
Quite a few
