> On 15 Mar 2016, at 02:13, Rob Nelson wrote:
>
> I've not seen a conflict with r10k, can you elaborate on that? Curious if I'm
> hitting it and not knowing it!
>
> However, I have seen it cause great confusion with modules like hunner/hiera
> or jlambert121/puppet that want to manage it, be
Puppet Agent 1.3.6 is now available! This is a security release that
updates OpenSSL to 1.0.2g, and addresses a number of recent CVEs.
See the release notes for the puppet agent package here:
http://docs.puppetlabs.com/puppet/latest/reference/release_notes_agent.html
To install or upgrade puppet-
I've not seen a conflict with r10k, can you elaborate on that? Curious if
I'm hitting it and not knowing it!
However, I have seen it cause great confusion with modules like
hunner/hiera or jlambert121/puppet that want to manage it, because there's
an ugly set of possible locations depending on oss
You’re right! I was confusing something else. Ignore my previous email.
Sent from my Windows 10 phone
From: Eric Sorenson
Sent: Monday, March 14, 2016 5:54 PM
To: puppet-dev@googlegroups.com
Subject: Re: [Puppet-dev] Signal boost on HI-490 - moving hiera.yaml
outofcodedir
On Mar 14, 2016, at 5
On Mar 14, 2016, at 5:48 PM, Eli Young wrote:
> One side effect of this change would appear to be the inability to use/test a
> new hiera, uh, hierarchy or backend in a feature branch without affecting the
> master branch.
But ... you already can't do that because the hierarchy's global. Unle
One side effect of this change would appear to be the inability to use/test a
new hiera, uh, hierarchy or backend in a feature branch without affecting the
master branch.
Sent from my Windows 10 phone
From: Eric Sorenson
Sent: Monday, March 14, 2016 5:43 PM
To: Puppet Developers
Subject: [Puppe
As a result of some introspection around r10k workflows, I came to agree
with the statement in the title of HI-490: "the location of hiera.yaml in
puppet-agent is a mistake." The root of the problem is that the current
hiera.yaml is a mixture of global configuration (datadir location, merge
beh
I know it's long past EOL/EOS but could you add in Puppet 2 at that URL?
The only EOS notice I could find is in a mailing list entry and it would be
nice to have a more official reference to it for doubters.
Rob Nelson
rnels...@gmail.com
On Mon, Mar 14, 2016 at 2:18 PM, Eric Sorenson wrote:
>
Yep, believe me it's under active discussion and we'll shout from the rooftops
once everything's sorted; part of the reason for the extension was that we
realised July was too close for comfort for a lot of customers.
--eric0
On Mar 14, 2016, at 11:16 AM, Trevor Vaughan wrote:
> Got it. Thank
Got it. Thanks Eric!
Please remember that a lot of places have a 30 to 90 day mandate to get off
of unsupported versions of software. Announcing this everywhere possible as
early as possible would be great so that the big machinery can get moving.
Thanks,
Trevor
On Mon, Mar 14, 2016 at 2:05 PM,
Hey Trevor, I'll reply over on the users list as well, but here it is: As a
practical matter we're going to have Puppet 3.8 on maintenance and security
fixes as long as there's a supported PE version that incorporates it. The
support lifecycle website[1] currently says July 2016 but we're highly
Yep, thanks for raising awareness.
This ticket looks like it might be addressed by (or should be considered
while reviewing) two active PRs:
* https://github.com/puppetlabs/puppet/pull/4770
* https://github.com/puppetlabs/puppet/pull/4755
Kylo
On Sun, Mar 13, 2016 at 11:08 PM, Eli Young wrote:
Hi All,
Sorry about the bad form but I popped this over on Users without any
response for a week.
Is there a current EOL estimate for the 3.X series? I've been seeing some
confusion with PE 3.8 and FOSS 3.8.
Thanks,
Trevor
--
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699
-- T
13 matches
Mail list logo
