PuppetDB 2.2.2 - October 21, 2014
PuppetDB 2.2.2 Downloads
Available in native package format in the release repositories at:
http://yum.puppetlabs.com and http://apt.puppetlabs.com
For information on how to enable the Puppet Labs repos, see:
http://docs.puppetlabs.com/g
PuppetDB 2.2.0 final - August 27th, 2014
PuppetDB 2.2.0 Downloads
Available in native package format in the release repositories at:
http://yum.puppetlabs.com and http://apt.puppetlabs.com
For information on how to enable the Puppet Labs repos, see:
http://docs.puppetlab
Hello,
Does anyone here happen to know if
https://github.com/puppetlabs/puppetdb-javaclient still happens to work
with puppetdb 1.5 via puppet enterprise? I have having difficulty making
the connection from the java client.
Specifically
Jul 11, 2014 6:32:11 AM org.apache.http.impl.client.Def
** Final Release **
PuppetDB 2.1.0 final - July 8th, 2014.
PuppetDB 2.1.0 Downloads
Available in native package format in the release repositories at:
http://yum.puppetlabs.com and http://apt.puppetlabs.com
For information on how to enable the Puppet Labs repos, see:
ht
** Final Release **
PuppetDB 2.0.0 final - May 6, 2014.
PuppetDB 2.0.0 Downloads
Available in native package format in the release repositories at:
http://yum.puppetlabs.com and http://apt.puppetlabs.com
For information on how to enable the Puppet Labs repos, see:
http:
PuppetDB 1.6.3 final - March 27th, 2014.
PuppetDB 1.6.3 Downloads
Available in native package format in the release repositories at:
http://yum.puppetlabs.com and http://apt.puppetlabs.com
For information on how to enable the Puppet Labs repos, see:
http://docs.puppetlab
PuppetDB 1.6.2 final - February 6th, 2014.
PuppetDB 1.6.2 Downloads
Available in native package format in the release repositories at:
http://yum.puppetlabs.com and http://apt.puppetlabs.com
For information on how to enable the Puppet Labs repos, see:
http://docs.p
PuppetDB 1.6.0 final
* RC1: January 7th, 2014.
* RC2: January 14th, 2014.
* RC3: January 22nd, 2014.
* Final: January 30th, 2014.
PuppetDB 1.6.0 Downloads
Available in native package format in the pre-release repositories at:
http://yum.puppetlabs.com and http://apt.
** Release Candidate **
PuppetDB 1.6.0-rc3
Prerelease: PuppetDB 1.6.0 is not yet released
* RC1: January 7th, 2014.
* RC2: January 14th, 2014.
* RC3: January 22nd, 2014.
PuppetDB 1.6.0-rc3 Downloads
Available in native package format in the pre-release repositories
On 2014-01-16 16:43, Ken Barber wrote:
I read through the comprehensive release notes trying to find if there are
any specific changes/additions that affects the API that I need to also
incorporate in the Java client (new endpoints or functionality). Lot's of
great additions for sure but am I cor
> I read through the comprehensive release notes trying to find if there are
> any specific changes/additions that affects the API that I need to also
> incorporate in the Java client (new endpoints or functionality). Lot's of
> great additions for sure but am I correct in assuming that the actual
I read through the comprehensive release notes trying to find if there
are any specific changes/additions that affects the API that I need to
also incorporate in the Java client (new endpoints or functionality).
Lot's of great additions for sure but am I correct in assuming that the
actual API
** Release Candidate **
PuppetDB 1.6.0-rc2
Prerelease: PuppetDB 1.6.0 is not yet released
* RC1: January 7th, 2014.
* RC2: January 14th, 2014.
PuppetDB 1.6.0-rc2 Downloads
Available in native package format in the pre-release repositories at:
http://yum.puppetlabs.c
** Release Candidate **
PuppetDB 1.6.0-rc1
Prerelease: PuppetDB 1.6.0 is not yet released
* RC1: January 7th, 2014.
PuppetDB 1.6.0-rc1 Downloads
Available in native package format in the pre-release repositories at:
http://yum.puppetlabs.com and http://apt.puppetlab
On Wed, Jun 12, 2013 at 8:44 AM, Deepak Giridharagopal
wrote:
> On Tue, Jun 11, 2013 at 7:52 PM, michael hancock wrote:
>>
>> On Tuesday, June 11, 2013 9:26:06 PM UTC-4, Dustin J. Mitchell wrote:
>>
>>> On Tue, Jun 11, 2013 at 12:41 PM, Daniel Pittman
>>> wrote:
>>> >> There should be a /latest/
On Tue, Jun 11, 2013 at 7:52 PM, michael hancock wrote:
> On Tuesday, June 11, 2013 9:26:06 PM UTC-4, Dustin J. Mitchell wrote:
>
> On Tue, Jun 11, 2013 at 12:41 PM, Daniel Pittman
>> wrote:
>> >> There should be a /latest/ link that points to the latest API version,
>> >> too. If such a thing
On Wed, Jun 12, 2013 at 1:11 AM, Mike Hancock wrote:
> If .../api/nodes is no longer defined in v3 then:
>
> get .../api/nodes
> Accept: version=3
>
> :returns 404
Well, we've painted this bikeshed enough to get it through the winter.
I don't expect to use the API myself, so I don't actually h
On Jun 11, 2013, at 23:57, "Dustin J. Mitchell" wrote:
> On Tue, Jun 11, 2013 at 9:52 PM, michael hancock wrote:
>> That is not what I asked for. The discussion is about alternative designs
>> for handling REST API versioning. For REST API's I see versioning as content
>> negotiation.
>>
>> Fo
On Tue, Jun 11, 2013 at 9:52 PM, michael hancock wrote:
> That is not what I asked for. The discussion is about alternative designs
> for handling REST API versioning. For REST API's I see versioning as content
> negotiation.
>
> For example,
>
> GET .../api/nodes
> Accept: version=2.0
>
> is like
On Tuesday, June 11, 2013 9:26:06 PM UTC-4, Dustin J. Mitchell wrote:
> On Tue, Jun 11, 2013 at 12:41 PM, Daniel Pittman
> >
> wrote:
> >> There should be a /latest/ link that points to the latest API version,
> >> too. If such a thing does not exist in PuppetDB, then I think that'd
> >> be
On Tue, Jun 11, 2013 at 12:41 PM, Daniel Pittman wrote:
>> There should be a /latest/ link that points to the latest API version,
>> too. If such a thing does not exist in PuppetDB, then I think that'd
>> be the better feature request to make.
>
> This would be a fundamental mistake, however. Wh
On Tue, Jun 11, 2013 at 7:43 AM, Dustin J. Mitchell wrote:
> On Tue, Jun 11, 2013 at 9:42 AM, michael hancock wrote:
>> I just noticed that the API version is embedded in the URL like:
>>
>> curl -H "Accept: application/json" http://puppetdb.domain/v2/nodes
>>
>> I suppose it's too late to imple
On Tue, Jun 11, 2013 at 12:16 PM, David Schmitt wrote:
> As if anybody who has enough configurations specifying an endpoint that
> changing the version number is a problem would be in the position to speak
> the current API at /latest/ everywhere at the same time.
The OP indicated they wanted to
On 11.06.2013 16:43, Dustin J. Mitchell wrote:
On Tue, Jun 11, 2013 at 9:42 AM, michael hancock wrote:
I just noticed that the API version is embedded in the URL like:
curl -H "Accept: application/json" http://puppetdb.domain/v2/nodes
I suppose it's too late to implement this so the client w
On Tue, Jun 11, 2013 at 9:42 AM, michael hancock wrote:
> I just noticed that the API version is embedded in the URL like:
>
> curl -H "Accept: application/json" http://puppetdb.domain/v2/nodes
>
> I suppose it's too late to implement this so the client would do:
>
> curl -H "Accept: application/
I just noticed that the API version is embedded in the URL like:
curl -H "Accept: application/json" http://puppetdb.domain/v2/nodes
I suppose it's too late to implement this so the client would do:
curl -H "Accept: application/json;version=2.0"
http://puppetdb.domain/api/nodes
I don't want t
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
(puppet-users is more appropriate for this question btw, next time use
that mailing list instead of this one).
'Connection refused' is a generic TCP message telling us that the port
is not open on the host you specified. This usually means its not
running, or not listening on the host port combina
Sonal,
There appears to be a problem that either puppetdb is not running, not
listening on the port/interface, or being blocked by a firewall and so the
connection to puppet db is being refused.
You should take this and your other question to the puppet-dev mailing
list. This list is mainly for d
When i m using puppetDB n Postgre sql database, following error is coming.
err: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed
to submit 'replace facts' command for abcd.example.com to PuppetDB at
puppet-DB.example.com:8081: Connection refused - connect(2)
--
You
When i m using puppetDB n Postgre sql database, following error is coming.
err: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed
to submit 'replace facts' command for abcd.example.com to PuppetDB at
puppet-DB.example.com:8081: Connection refused - connect(2)
--
You
On Tuesday, January 8, 2013 at 5:10 AM, Erik Dalén wrote:
> I've been reading through the experimental PuppetDB reports API and I feel a
> lot of stuff is missing in it. I know it is experimental and kind of beta
> still, but I thought it might be good to share some feedback on it anyway.
>
> I
I've been reading through the experimental PuppetDB reports API and I feel a
lot of stuff is missing in it. I know it is experimental and kind of beta
still, but I thought it might be good to share some feedback on it anyway.
In the report API
(https://github.com/puppetlabs/puppetdb/blob/master
On Wed, Aug 29, 2012 at 02:26:39PM +0200, David Schmitt wrote:
I just noticed that a problem I had in my manifests -- when talking to
puppetdb -- were tags that contained upper-case letters. The tag is stored
downcased, but the query is the original (non-matching) casing.
Example:
file { "/tm
On Wed, Aug 29, 2012 at 01:11:26PM +0200, David Schmitt wrote:
Hi,
I was just hunting down a really nasty dependency problem, which could
only be found by this patch:
--- /tmp/puppetdb.rb.orig 2012-08-29 07:09:44.680687865 -0400
+++
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/catalog/p
Hi,
I just noticed that a problem I had in my manifests -- when talking to
puppetdb -- were tags that contained upper-case letters. The tag is stored
downcased, but the query is the original (non-matching) casing.
Example:
file { "/tmp/test": ensure => present tag => "pdsh::node::ABC" }
File
Hi,
I was just hunting down a really nasty dependency problem, which could
only be found by this patch:
--- /tmp/puppetdb.rb.orig 2012-08-29 07:09:44.680687865 -0400
+++
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/catalog/puppetdb.rb
2012-08-29
07:09:54.069673455 -0400
@@ -160,7 +1
Due to a packaging error, the packaged rpms of puppetdb contained old
source files. New packages (0.9.1-2) have been uploaded to
yum.puppetlabs.com. Please let us know if you have any issues.
--
Matthaus Litteken
Release Manager, Puppet Labs
--
You received this message because you are subscrib
38 matches
Mail list logo
