Initial version of puppetdb v4

[russell]

Hi,

This commit is probably incomplete, i haven't had a chance to check all the existing v3 APIs that will be exposed by the v4 subclass. But I thought it might be a good idea to get some feedback about what i have done so far. Would this be something that you would be willing to merge upstream?

Cheers,
Russell

[coveralls]

Changes Unknown when pulling b8a82a1 on NeCTAR-RC:master into * on nedap:master*.

[daenney]

I think we're going to run into a few issues here because of what's changed on v4, namely the environments support which we need to account for in the objects.

[russell]

Ah, i see what you are talking about.... the __query_scope variable? I can extend the patch to cover that.

Do you think we should try and get some more integration style tests with some example json parsing into objects from each of the different versions?

[daenney]

Yes, that would be a good step forward. I'm considering using betamax to record from a live session against PuppetDB and then simply replay those whenever we run the tests.

[hggh]

any news on pypuppetdb support v4?

[corey-hammerton]

Any updates?

[daenney]

This would need quite a bit of rework, and some other parts of PuppetDB too, in light of the 3.x release of PuppetDB. I don't think it's worth the effort supporting two "versions" of the v4 API. As such we're probably better off abandoning this and keeping 2.x support up to and including v3 and releasing a new major version of pypuppetdb that drops the legacy baggage and talks to PuppetDB 3.x over v4.

[corey-hammerton]

I will be able to work on this as a side project of mine. I will create a fork of this repository and work on it there while testing against a PuppetDB 3.x instance on a test environment.