I've expanded the README a bit now and release 1.0.0-pre2 which should make it 
a bit easier to use.

It only supports queries over SSL and uses the Puppet HTTP methods for making 
connections. So if your Nginx uses a external CA cert you might be running into 
bug #15561 http://projects.puppetlabs.com/issues/15561 .

In the new 1.0.0-pre2 I've added the ability to use other kinds of HTTP 
connection objects though and use a regular one in the find-nodes binary, so 
you can try that instead of the puppet face if you are still getting SSL 
errors.  

--  
Erik Dalén


On Thursday 28 March 2013 at 17:31, Stephen Price wrote:

> Guys, Can you expand the README to describe where this should be run from? 
> I've been trying to use it as a Puppet Face from different hosts, including 
> directly on the PuppetDB server, to no avail. I keep getting 'bad request' or 
> SSL cert errors. My PuppetDB is running on localhost:8080 with Nginx (with 
> SSL) as the frontend. It'd be nice if this Face was usable from any Puppet 
> node, or at least from the Puppet Master.
>  
> On Monday, March 4, 2013 7:59:30 AM UTC-8, Erik Dalén wrote:
> > I've released version 1.0.0-pre1 of the dalen-puppetdbquery module, it 
> > includes the old functions against the PuppetDB api version 1.0. But also 
> > some entirely new functions that will query the PuppetDB api v2.0 (in 
> > puppetdb 1.1 and up).  
> >  
> > These new functions borrow the syntax from Dan Bode's ruby-puppetdb, but 
> > are entirely rewritten to make use of the 2.0 API.  
> >  
> > It now uses a lexer and parser written in rex & racc (ruby versions of lex 
> > & yacc) to compile a high level query language into PuppetDB queries.  
> >  
> > An example of a high level query would be:  
> > Class[Apache]{service_enable=true} and (osfamily=Redhat or osfamily=Debian) 
> >  
> >  
> > That would find any host with the apache class (notice though that class 
> > names have to be capitalized in queries) with the parameter service_enable 
> > => true and osfamily red hat or debian. It does normal operator precedence, 
> > so a parenthesis is required around that or-statement.  
> >  
> > The three new query functions are:  
> > * query_nodes  
> > * query_facts  
> > * query_resources  
> >  
> > So far only query_nodes and query_facts accept the new query language. In 
> > all three functions an array argument instead of string will be treated as 
> > a "raw" puppetdb query.  
> >  
> > Anyway, please test it and send me feedback (dalen on freenode). The old 
> > functions are left intact but deprecated, so it shouldn't affect any 
> > existing code using the older functions.  
> >  
> > --  
> > Erik Dalén  
>  
> --  
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] 
> (mailto:[email protected]).
> To post to this group, send email to [email protected] 
> (mailto:[email protected]).
> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>  
>  



-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to