Puppetboard is an excelent radiator of information, but sometimes
we want to expose information to users we don't trust giving full
access to the PuppetDB query language.
I would reccomend that Puppetboard be run twice. One, with query
enabled, run on a port behind apache login. Another, with query
disabled, run unproxied for the unwashed masses.
Closes#10.
Recently changes were made to pypuppetdb to support, at a basic level,
the v3 API introduced with PuppetDB 1.5.
This commit changes some internals of Puppetboard to handle the new
situation:
* The experimental endpoints are gone, so is the ExperimentalDisabled
Error;
* v2 API can no longer access Reports/Events so we now check that we're
talking at least v3 API;
* Introduce a configuration setting PUPPETDB_API which takes an integer
repersenting the API version we want to talk.
