+1 for me
On Friday, September 11, 2015 at 12:26:25 PM UTC-5, Daniele Sluijters wrote:
>
>
> Want to join? Throw a +1 in the list so I get a rough idea of how people
> are going to show.
>
> Can't join on Tuesday the 6th of October at 15:30 because you're not in
> town yet? Not a problem,
Awesome news! Especially love the full data available in DB and native
failover support, my hacky standby mode can finally DIAF :)
On Thursday, July 9, 2015 at 6:16:30 PM UTC-5, Wyatt Alt wrote:
PuppetDB 3.0.0 - July 9, 2015
PuppetDB 3.0.0 Downloads
Available in
One could ague puppetlabs is better off sharing the package specs for
included rubies so people can keep them current themselves, security
updates directly from ruby vs having to wait for downstream backports and
vendor repos sounds better to me long term. Not only can puppetlabs push
updates
I don't see these negatives at all. I think having puppet decoupled is a
good thing - for reliability, management and freeing us from ruby hell.
I can't see an AIO package altering the native behavior of the OS or
system rubbies either..
Since it is OSS as well, is there a reason you wouldn't
Awesome! Off to go pull it down and give it a spin!
On Friday, December 5, 2014 4:47:49 PM UTC-6, Alice Nodelman wrote:
beaker 2.0 and beaker-rspec 4.0 are now released and available publicly
from rubygems.
These updates to beaker and beaker-rspec EOL ruby 1.8, update minitest
dependency
Yay!
On Tuesday, November 18, 2014 7:11:03 PM UTC-6, Michael Stanhke wrote:
We'll be picking one Ruby (2.1.z), and using that everywhere for a
consistent stack.
--
You received this message because you are subscribed to the Google Groups
Puppet Developers group.
To unsubscribe
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 configuration/feature flag that says hey puppet, we're
you are seeing?
thanks,
Josh
On Tue, Jun 17, 2014 at 2:28 AM, Stefan Heijmans heij...@gmail.com
javascript: wrote:
Aha, experienced the same thing last week, didn't have time to look into
it yet...
On Monday, June 16, 2014 3:30:31 PM UTC+2, Byron Miller wrote:
Running puppet 3.6.2
Running puppet 3.6.2 and disable_warnings = deprecations appears to make no
difference to prohibiting the alert about environments.
On Tuesday, June 10, 2014 1:19:05 PM UTC-5, Moses Mendoza wrote:
Puppet 3.6.2 is a security and bug fix release in the Puppet 3.6
series. This release addresses
