We’re happy to announce the 2.7.1 release of Puppet Server. This is a
backward compatible bug fix release.
NOTE: If you are upgrading to version 2.7.1 from a version earlier than 2.5.
0 and you have modified the "bootstrap.cfg" file, please read this
document before proceeding with the upgrade: h
Hi! We’re happy to announce the new 2.5.0 release of Puppet Server. This
is a backward compatible feature release that also contains a few bug
fixes. Highlights include:
-
New workflows for certificate signing and authentication, based on
improved support for X.509 authorization exte
Hi,
tl;dr: naming stuff is hard, we're hoping to rename the puppet-server git
repo to puppetserver sometime soon (tomorrow?). Github should handle
redirects in a way that will hopefully mean that this change is effectively
invisible to anyone who has a fork, but if anyone has any concerns, please
On Wed, Mar 9, 2016 at 12:45 PM, Chris Price wrote:
> Hello,
>
> We're looking into the possibility of deprecating and removing the `
> resource_types` endpoint from Puppet Server.
>
Bump... haven't heard any objections to deprecating and removing the
resource_type
need to do to be ready for that whenever we start lining up dates for
future major version bumps.
>
> On Wed, 9 Mar 2016 at 21:45 Chris Price wrote:
>
>> Hello,
>>
>> We're looking into the possibility of deprecating and removing the `
>> resource_types` en
Hello,
We're looking into the possibility of deprecating and removing the `
resource_types` endpoint from Puppet Server.
The current implementation can return information about a lot of different
things in Puppet, but it's very expensive (in terms of CPU and memory
usage), and has some unexpected
On Fri, Jan 29, 2016 at 8:16 AM, Alex Harvey wrote:
> Yep, it's solved in Puppet 4 - the all-in-one package is fantastic, as is
> so much in Puppet 4. However PE hasn't release Puppet 4 yet;
>
OSS Puppet 4 was released almost a year ago. Puppet 4 shipped in PE
2015.2.0 in July of last year. T
On Fri, Sep 11, 2015 at 10:20 AM, Daniele Sluijters
wrote:
> Hi everyone,
>
> As is tradition (since last year) I'm organising a pre-contributor-summit
> tea party at some decent tea place in Portland. We shall assemble at the to
> be announce tea shop at 15:30 local time.
>
> If you live in Port
On Thu, Jul 16, 2015 at 2:34 PM, Trevor Vaughan
wrote:
> Thanks Chris, this is both helpful and reassuring.
>
> DOCUMENT-389 for fake Internet points.
>
42 fake internet points awarded; thank you!
>
> Trevor
>
> On Thu, Jul 16, 2015 at 6:46 AM, Chris Price wrote:
&
On Thu, Jul 16, 2015 at 8:56 AM, Nan Liu wrote:
> On Wednesday, July 15, 2015 at 7:06:42 PM UTC-7, Trevor Vaughan wrote:
>>
>> So, we ran across this one today and I dug up the thread where Felix
>> Frank, John Bolinger, and I all agreed (https://goo.gl/LQ20bj) that
>> there were solid use cases
On Mon, Jul 6, 2015 at 3:55 PM, John Bollinger
wrote:
>
> On Friday, July 3, 2015 at 2:25:15 AM UTC-5, Chris Price wrote:
>
>
>> I have a question / thought experiment related to this, and would really
>> love to hear some feedback from the community:
>>
>>
On Fri, Jul 3, 2015 at 10:13 AM, Erik Dalén
wrote:
>
>
> On Fri, 3 Jul 2015 at 11:05 Chris Price wrote:
>
>> On Fri, Jul 3, 2015 at 9:50 AM, Erik Dalén
>> wrote:
>>
>>>
>>>
>>> On Fri, 3 Jul 2015 at 09:25 Chris Price wrote:
>>>
On Fri, Jul 3, 2015 at 9:50 AM, Erik Dalén
wrote:
>
>
> On Fri, 3 Jul 2015 at 09:25 Chris Price wrote:
>
>>
>>
>> On Monday, June 29, 2015 at 6:02:17 PM UTC+1, Luke Kanies wrote:
>>>
>>> On Jun 29, 2015, at 8:43 AM, Raphaël Pinson
>>> w
On Monday, June 29, 2015 at 6:02:17 PM UTC+1, Luke Kanies wrote:
>
> On Jun 29, 2015, at 8:43 AM, Raphaël Pinson > wrote:
> >
> > Hello,
> >
> >
> > I've activated caching on our Puppetservers, using the admin API to
> invalidate the cache upon deploying new environments. However, this onl
On Mon, Mar 9, 2015 at 10:15 AM, Brice Figureau <
brice-pup...@daysofwonder.com> wrote:
> On Mon, 2015-03-09 at 08:52 -0700, Chris Price wrote:
> >
> > This sounds great, thanks a ton for putting it together! I'll try to
> > get some reviews going, and maybe at
On Mon, Mar 9, 2015 at 1:59 AM, Brice Figureau <
brice-pup...@daysofwonder.com> wrote:
>
> I think I've completed a milestone in respect with what you wanted and
> SERVER-111:
>
> https://github.com/masterzen/trapperkeeper-authorization
>
>
> I've tried to put the better documentation I could in t
On Fri, Mar 6, 2015 at 8:46 AM, Eric Thompson wrote:
>
>> Currently there are two separate certificate authority implementations,
>> one in Ruby and one in Clojure. Puppet 5 will consolidate onto the new
>> Clojure CA, removing the Ruby CA code and building new command-line tools
>> to interact w
On Fri, Mar 6, 2015 at 6:41 AM, Erik Dalén
wrote:
>
> Also a solution to https://tickets.puppetlabs.com/browse/SERVER-115 is
> really needed. It can sort of be solved in the Ruby version by only using a
> single worker instance.
>
This is definitely slated for Puppet 5.0/Puppet Server 3.0.
>
>
On Tue, Feb 24, 2015 at 2:48 AM, Brice Figureau <
brice-pup...@daysofwonder.com> wrote:
> On Mon, 2015-02-23 at 06:57 -0800, Chris Price wrote:
> > On Sun, Feb 22, 2015 at 9:18 PM, Eric Sorenson
> > wrote:
>
> How about this:
>
> rules {
> "/pa
On Mon, Feb 23, 2015 at 1:30 PM, Trevor Vaughan
wrote:
Well, without 'include' statements, you'd better add some ordering to your
> puppetlabs-hocon module.
>
> Currently, auth.conf is order dependent and I don't really see how you're
> going to change that (so you probably need ordering anyway).
On Mon, Feb 23, 2015 at 9:39 AM, Trevor Vaughan
wrote:
> That works. I just put in a feature request against Hiera for a HOCON
> native back end :-D.
>
Good idea!
Also, if you'd pop out some native types that can manipulate these things,
> that would be nifty.
>
This should probably be conside
to
standardize on going forward. :) Also, the current auth.conf format is
none of the above, so moving it to any of the above would mean 'n - 1'
formats :)
>
> On Mon, Feb 23, 2015 at 9:57 AM, Chris Price wrote:
>
>> On Sun, Feb 22, 2015 at 9:18 PM, Eric Sorenson &
On Sun, Feb 22, 2015 at 9:18 PM, Eric Sorenson wrote:
>
> Hi Brice! This project is really cool, thanks for taking it on. I have a
> few comments about requirements and design that I hope can save some work
> and make it easier to include this upstream once it's done.
>
> I went back and surveyed
On Mon, Dec 29, 2014 at 4:20 AM, Brice Figureau <
brice-pup...@daysofwonder.com> wrote:
> Hi,
>
> I'm still playing with my file_metadata implementation, and want to
> provide the 'modules' special mount. This mount requires finding the
> module path of a given environment in the clojure part.
>
>
On Sat, Dec 27, 2014 at 8:39 AM, Brice Figureau <
brice-pup...@daysofwonder.com> wrote:
> Hi all,
>
> I've started coding the file_metadata terminus as a pure clojure service
> in the puppet-server and have a few existencial questions.
>
> I have a basic fileserver.conf parsing system, mount findi
On Mon, Nov 17, 2014 at 6:22 AM, Byron Miller wrote:
> I for one would love to feel more safe when tempting fate upgrading my
> puppet infrastructure. I like the idea of rolling upgrades (if upgraded,
> point here), but i would love to have some sort of process in puppet to
> handle this. A confi
On Fri, Nov 14, 2014 at 4:02 PM, Erik Dalén
wrote:
>
>
> On Fri Nov 14 2014 at 7:16:07 PM Felix Frank <
> felix.fr...@alumni.tu-berlin.de> wrote:
>
>> On 11/14/2014 07:09 PM, Henrik Lindberg wrote:
>> >
>> > Please note that some changes in puppet 4 mean that puppet 3 agents
>> > won’t be able to
On Fri, Oct 17, 2014 at 11:28 AM, Trevor Vaughan
wrote:
> Both would be nice. Or even in a DEBUGGING_README or somesuch at the top
> level of the installation directory structure.
>
>
Good idea, thanks.
--
You received this message because you are subscribed to the Google Groups
"Puppet Develo
On Fri, Oct 17, 2014 at 10:15 AM, Trevor Vaughan
wrote:
> +1 for including everything that you need in your own private path.
>
> However, please make it VERY clear as to where these files are so that
> ninja patches can happen without hours of hunting.
>
>
Sounds good, what'd you have in mind?
" which is recursively searched.
>
> os-settings: {
> ruby-load-path: [ /usr/lib64/ruby/vendor_ruby/2.0.0,
> /usr/lib64/ruby/site_ruby/2.0.0,
> /usr/lib64/ruby/gems/2.0.0/gems/hiera-1.2.1/lib
> ]
> }
> --
On Fri, Oct 17, 2014 at 7:21 AM, Darin Perusich wrote:
> Hi Chris,
>
> Much like how installing puppetserver from yum.puppetlabs.com would
> leverage the hiera package for hiera support, I need the same as I'm
> packaging it in the open build service for opensuse/sles.
>
> I've tried added it to
Hi Darin,
Puppet Server doesn't currently support multiple directories for gem home;
we try to avoid using gems from the system ruby because we want to make
sure that all gems are installed via the JRuby interpreter embedded in
Puppet Server. This helps us guarantee that the gems will be compatib
On Mon, Sep 29, 2014 at 1:39 PM, Darin Perusich wrote:
> Progress...after making that change to the project.clj and building
> it's now failing to start with this error. Hopefully I can dig into
> this a bit more tomorrow, but puppetdb has been working fine on this
> system.
>
> ArgumentError: Co
On Mon, Sep 29, 2014 at 1:25 PM, Trevor Vaughan
wrote:
> Any docs on the configuration files?
>
Coming this week! :) Keep an eye on the repo.
>
> Is there a way to update webserver.conf to run a CA on a different port
> and, instead of having 'want' in the client_auth section having somethin
On Mon, Sep 29, 2014 at 1:33 PM, Andy Parker wrote:
> On Mon, Sep 29, 2014 at 1:00 PM, Josko Plazonic
> wrote:
>
>> Hullo,
>>
>> On 09/23/2014 12:11 PM, Nate Wolfe wrote:
>>
>>> As the version number 0.2.0 should imply, Puppet Server is not
>>> production ready (yet), but please
>>> do try it ou
On Fri, Sep 26, 2014 at 3:06 AM, Dominic Cleal wrote:
>
> The only hitch I've had was with the Foreman report processor, which
> makes an HTTPS connection to Apache with mod_ssl. On new OSes with
> modern mod_ssl versions (e.g. EL7 or Ubuntu 14.04), the report processor
> fails to make an HTTPS
On Mon, Sep 29, 2014 at 2:26 PM, Chris Price wrote:
> On Mon, Sep 29, 2014 at 12:44 PM, Trevor Vaughan
> wrote:
>
> Maybe check your memory settings? We currently ship with a pretty large
> default heap size, and we don't handle it very gracefully if you don't have
&
On Mon, Sep 29, 2014 at 12:44 PM, Trevor Vaughan
wrote:
> Ugh, it would probably work better if I actually looked at my notes prior
> to sending a message instead of trying to go from memory.
>
> SELinux is fine.
>
> Sorry for the false alarm.
>
> I did have the server crash at some point and I'm
On Mon, Sep 29, 2014 at 12:00 PM, Trevor Vaughan
wrote:
> Well, I've given 0.2.0 a run and, while it seems to function properly,
> it's throwing AVCs all over the place.
>
> Any ETA for a working policy set?
>
> Also, it's not quite 100% matching the 3.6 language set but I'll have to
> play with
On Mon, Sep 29, 2014 at 7:17 AM, Darin Perusich wrote:
> Here's a quick recreation of the steps. This is on OpenSUSE 13.1 with
> OpenJDK 1.7.0_51
>
> https://gist.github.com/deadpoint/900a2d92911705023986
> --
> Later,
> Darin
>
Hi Darin,
The issue you're seeing is because the "tk-jetty9" depen
PuppetDB 1.5.2 is now available for download! This is a maintenance and
bugfix release.
=
## Downloads ##
=
Available in native package format at:
http://yum.puppetlabs.com and http://apt.puppetlabs.com
Puppet module:
http://forge.puppetlabs.com/puppetlabs/puppetdb
Sour
wrote:
> >>>
> >>> No packages for precise/raring? Its missing debs for 1.5.0. Lucid seems
> >>> fine
> >>>
> >>> Thanks,
> >>> William
> >>>
> >>>
> >>> On Mon, Sep 30, 2013 at 4:56 PM, Chris Price
&
PuppetDB 1.5.0 is now available for download! This is a new feature
release that contains a few bug-fixes as well.
=
## Downloads ##
=
Available in native package format at:
http://yum.puppetlabs.com and http://apt.puppetlabs.com
Puppet module:
http://forge.puppetlabs.co
Hi Darin,
That's... not ideal. Sorry.
We don't usually build it that way, though. What, specifically, are you
trying to build? Just the jar file? If so, what you really want to do is
run `lein uberjar`. It looks like there's a small glitch around how we
name that file, though. The easiest w
it seems it is not effective yet - maybe doing
> something wrong.
>
>
> On Wednesday, 10 July 2013 16:34:32 UTC+3, Chris Price wrote:
>
>> Hi Joseph,
>>
>> Based on this line:
>>
>> SERVER: Failed to submit 'replace facts' command for
>> pp
Hi Joseph,
Based on this line:
SERVER: Failed to submit 'replace facts' command for
pptconsole.ca.local to PuppetDB at pptconsole.ca.local:8081: No route to
host - connect(2)
It sounds as though you may have a DNS issue. If you log in to your puppet
master VM, are you able to ping 'pptconso
PuppetDB 1.3.2 is now available for download! This is a very minor
compatibility release for the 1.3 series of PuppetDB.
===
## Downloads ##
===
Available in native package format at:
http://yum.puppetlabs.com and http://apt.puppetlabs.com
Puppet module:
http://forge.pup
issues
# See our development board on Trello:
http://links.puppetlabs.com/puppetdb-trello
## PuppetDB 1.3.1 Release Notes ##
Many thanks to the following
people who contributed patches to this release:
* Chris Price
* Deepak Giridharagopal
Andy,
Sorry, for some reason when I was reviewing that pull request I was
thinking it was targeted at our AIX branch. I probably should have checked
with your team before merging it. If you guys decide that we should back
that out and solve the problem a different way, we will be happy to work
wi
Erik, thanks a ton for adding these tickets! Very helpful.
On Thu, Apr 25, 2013 at 3:22 AM, Erik Dalén wrote:
> Now that the patch to support structured facts in puppet itself is merged
> it needs to be supported in puppetdb quite soon.
> So I created a couple of tickets for how I think a possi
Actually, puppet is only going to attempt to connect to puppetdb on the SSL
port, so the setting in jetty.ini that you'll want to look at is the
"ssl-host" setting. The "host" one will also be useful if you'd like to be
able to access the PuppetDB dashboard in a browser.
On Mon, Feb 4, 2013 at 5
On Mon, Oct 22, 2012 at 12:27 PM, Andy Parker wrote:
> On Mon, Oct 22, 2012 at 12:05 PM, Chris Price
> wrote:
>
> Out of curiosity, why wasn't run_mode a parameter that was passed to
> initialize_settings?
>
At the time, I think I was assuming that anyone who was
My intention when I was last working on this stuff was that you could
simply call "Puppet.initialize_settings" (perhaps after calling
Puppet.run_mode=), and that the rest
of the ugly internal stuff (initialize_application_defaults, etc.) would be
abstracted away.
However, I'm not entirely sure whe
o me the master and agent functionality are
> completely distinct and should remain so--or at least allow us to keep them
> separate at our sites.
>
> On Jun 25, 2012, at 2:18 PM, Chris Price wrote:
>
> We've been doing some work lately to harden the pluginsync functionality
>
Hi everyone,
We've been doing some work lately to harden the pluginsync functionality
for Puppet 3.x. An issue was brought to my attention by Jeff McCune:
In current versions of puppet, it's possible to configure things like your
vardir and libdir in any section of the config file; potentially,
single
module, your plumbing vs. porcelain issue would be satisfied, would it not?
On Tue, May 29, 2012 at 11:46 PM, David Schmitt wrote:
> On Tue, 29 May 2012 11:38:37 -0700, Chris Price
> wrote:
> > Thanks, David. I think that something along these lines is where we
> will
>
:
> On 2012-05-25 19:44, Chris Price wrote:
>
>> I'm surveying the landscape of existing puppet modules that have to do
>> with relational database functionality. I've talked with a few folks
>> now and it seems like there is a fairly broad range of opinions on wh
me":
> ensure => present,
> database => 'puppet',
> tag => "$puppet::params::database_server",
> }
>
> In the postgres module we have:
>
> postgres::createuser {'name':
> password => 'blah'
harder and puppetlabs will probably end up
> carrying more of the load of building this module up front than you would
> with database specific ones, but the benefits are definitely worth it.
>
> On Fri, May 25, 2012 at 1:44 PM, Chris Price wrote:
>
>> Hey folks,
>>
>> I
Hey folks,
I'm surveying the landscape of existing puppet modules that have to do with
relational database functionality. I've talked with a few folks now and it
seems like there is a fairly broad range of opinions on what "ideal" would
look like w/rt managing rdbms with puppet.
At one extreme,
s/fairly/fairly easily/
On Fri, May 25, 2012 at 9:33 AM, Chris Price wrote:
> On Thu, May 24, 2012 at 11:27 PM, Jeff Weiss
> wrote:
>
> Facter itself will not use the cache. If you have an application that
>> needs facts and needs them quickly, you may read the yaml file
On Thu, May 24, 2012 at 11:27 PM, Jeff Weiss
wrote:
Facter itself will not use the cache. If you have an application that
> needs facts and needs them quickly, you may read the yaml file on disk.
On Fri, May 25, 2012 at 3:38 AM, Ken Barber wrote:
And from memory PE already does this.
I m
On Wed, May 23, 2012 at 4:01 PM, Jeff Weiss wrote:
>
>
With Facter as both an executable and a library, it turns out to be really
> hard to be able to guarantee that a value will definitely be returned
> within a certain amount of time *and* if it takes longer than that reliably
> spawn something
Sweet! Glad that worked out.
On Wed, May 23, 2012 at 5:52 PM, Jeff McCune wrote:
> Nevermind, I think I have a good solution in:
>
> https://github.com/puppetlabs/puppet/pull/812
>
> Huzzah for having a TestHelper class in Puppet!
>
> -Jeff
>
>
> On Wed, May 23, 2012 at 5:38 PM, Jeff McCune wr
Just as a heads up--there have been some minor changes to that code in
puppet over the last few months. (Particularly, some special handling of
the case where the "~" character appears in the user's PATH.) I am not
sure if these changes are relevant to facter (because I don't think Facter
is doin
We have an implementation of "which" in puppet, and, IMO, it would make
sense for both projects to share the same code and logic for this.
However, our project structure doesn't currently lend itself to that.
If you do decide to implement a 'which', you might just copy the one from
puppet. I'm n
p.s., if we do go down this path it would be interesting to see if there is
some sort of existing library or standard specification for boolean logic
expressions that we could piggy-back off of, rather than rolling our own.
On Wed, May 16, 2012 at 1:05 PM, Chris Price wrote:
> Aren'
Aren't we, in effect, introducing another (mini, boolean) language with
this sort of proposal, though? I agree that the generality and flexibility
is appealing, but the idea of designing and supporting another parser /
lexer gives me pause.
Not to say that the benefits might not be worthwhile...
I think it belongs in puppet/blah/TestHelper.rb. This way the individual
version of puppet that has the dependency is specifying it and initializing
it... puppetlabs_spec_helper doesn't need to know anything about it. It's
only job is to say "Hey, puppet! Do whatever it is that you need to do to
On Mon, May 14, 2012 at 6:19 AM, Ken Barber wrote:
>
> So when I roll back to c9386b541e9ecf6c0daffde2825bad385ea4da2b I'm
> all good again. I've put in a work-around:
>
> c.before :each do
>Puppet[:data_binding_terminus] = 'none'
> end
>
> Which works smashingly ... but its a workaround, a
I'm not an expert on the topic, but my understanding is that you can't
create a type without well-defined property/parameter names. Or, to put it
a different way, there is currently no officially sanctioned means by which
to support dynamic property/parameter names for a type or a provider.
One w
Just FYI, there is some discussion of a partially-overlapping concern going
on in this ticket:
http://projects.puppetlabs.com/issues/13210
On Wed, May 2, 2012 at 12:04 PM, Dan Bode wrote:
>
>
> On Wed, May 2, 2012 at 9:11 AM, Andrew Parker wrote:
>
>> It can also be asked as "is passing nil or
Hello all,
We're working on some minor changes to the API for the resource_type
service (indirector) for Telly. One of the main goals here is to improve /
enable support for parameterized classes in external tools by making it
easier to request information about them.
The proposed changes that w
, Apr 17, 2012 at 6:11 PM, Chris Price wrote:
>
>> Doh. I didn't click through to your gist before I replied. It looks
>> like you've already identified the problematic test, so most of what I
>> posted will be of no use to you. :(
>
>
> Well, I know my test
Doh. I didn't click through to your gist before I replied. It looks like
you've already identified the problematic test, so most of what I posted
will be of no use to you. :(
On Tue, Apr 17, 2012 at 5:27 PM, Jeff McCune wrote:
> Hey everyone,
>
> I'm working on fixing up a module and I've wri
Nick Lewis has a script that you can grab from here:
https://gist.github.com/1217637
If you know the order that your tests ran it, this will help you narrow it
down to the particular two that are interfering with one another
(accomplished via a sort of binary search, running half of the number of
Sorry about that--sent the e-mail to two different lists, one internal to
puppet. There were a couple of responses there, and the general consensus
seems to be:
1) It should not cause too many waves to disallow faces from defining
command-line options with the same names as built-in puppet option
Howdy folks... in the spirit of using this list for things other than
github spam:
I have another topic that I'd like to get feedback on with regards to
Puppet's settings management. (I know, you've all been eagerly awaiting
the next installment in this saga!)
Currently there is no mechanism in
Update: a little more digging reveals that the original selinux symlink
code came as a result of this ticket:
http://projects.puppetlabs.com/issues/2791
Still interested in feedback if anyone has any.
On Fri, Apr 6, 2012 at 12:58 PM, Chris Price wrote:
> Hey folks,
>
> I am revi
Hey folks,
I am reviewing the following pull request, which has to do with how puppet
deals with symlinks in selinux:
https://github.com/puppetlabs/puppet/pull/563
Just wondering if there is anyone out there who considers themselves strong
with selinux who has an opinion on this one way or the o
Yeah. Probably better to be safe than sorry. I'll plan on adding the
deprecation warning to Telly and then probably open a new ticket for
implementation, and we can slot that in to a later roadmap.
On Mon, Apr 2, 2012 at 10:09 AM, Randall Hansen wrote:
> On Mon, Apr 2, 2012 at 9:43 AM, Andrew P
isn't nil.
>
> Are we going to deprecate this for all of Telly and then change it in
> the next major release? Given the amount of anecdotal pain we've had
> in this area, is it feasible to admit we got this wrong and start
> deprecating in 2.7.x ?
>
>
>
> On W
Hi all,
I'm reviewing a ticket related to how we handle "undef" when it is passed
to a puppet function. The current behavior is to convert it to an empty
string before passing it off to the function body, but I'm not sure that's
the right thing to do as it seems to eliminate the ability to handle
Ugh. copy/paste failure... the pull request relating to config/settings is
this one:
https://github.com/puppetlabs/puppet/pull/571
On Tue, Mar 20, 2012 at 4:20 PM, Chris Price wrote:
> I sent a few e-mails out over the last week or so soliciting input /
> concerns re: some proposed c
I sent a few e-mails out over the last week or so soliciting input /
concerns re: some proposed changes to how puppet will handle config files /
settings definitions in Telly. Just a heads up that the changes that were
discussed are now in a pull request that should get merged in the next week
or
Hello,
We're leaning towards a small change in the behavior of how puppet finds
its config files for puppet 3.x.
Here is the situation: the current mechanism that we use (assuming the
config file is not explicitly specified on the command line) is a little
convoluted, and involves the value of "r
Dear dev,
We're considering some housekeeping changes to the code in puppet's main
"settings.rb" and "defaults.rb". The goal would be mainly to make the
setting definitions more consistent and a little more "strongly typed".
These changes should be entirely backwards-compatible, and transparent
blem is?
>
> thanks
>
> - Original Message -
> > From: "Chris Price"
> > To: puppet-dev@googlegroups.com
> > Sent: Tuesday, February 7, 2012 5:36:19 PM
> > Subject: [Puppet-dev] mocha issues
> >
> > Hi all,
> >
> >
> > Just an FYI
Hi all,
Just an FYI, Patrick and I discovered a pretty major bug in mocha versions
0.10.2 and 0.10.3 that will cause false positives on your rspec runs. The
Jenkins machines seem to be mostly running 0.9.12, which is not affected by
this bug--so hopefully we're not at risk of errors being masked
OK, thanks. It should be a fairly easy fix, and I should be able to get to
it in the next day or so.
On Tue, Feb 7, 2012 at 8:49 AM, Michael Stahnke wrote:
> On Tue, Jan 31, 2012 at 11:06 AM, Chris Price
> wrote:
> > https://projects.puppetlabs.com/issues/12336
> >
>
https://projects.puppetlabs.com/issues/12336
Hello,
As a result of a recent change to how we handle user-related environment
variables when we launch processes from puppet (see:
https://projects.puppetlabs.com/issues/5224 ), a bug was introduced wherein
an exception will be thrown if the followin
91 matches
Mail list logo
