The cause of this issues is that we introduced our own HTTP connection
wrapper in 3.0 (rather than using Net::HTTP directly). This allows us to
do a better job of centralizing the logic related to managing SSL setup and
Our Connection class provides a subset of the methods available on Ruby's
HTTP class, and it looks like puppetdbquery is using one of the methods
that don't currently exist in our new API.
The possible solutions would be to add the missing #start method to our new
class, or to tweak puppetdbquery so that it doesn't rely on the #start
method. I'll ping the folks on our platform team and see what their
Thanks for the heads up!