pypuppetdtb is a library to work with PuppetDB's REST API. It is implemented using the requests library.
This library is a thin wrapper around the REST API providing some convinience functions and objects to request and hold data from PuppetDB.
- To use this library you will need:
- Python 2.6 or 2.7
- Python 3.3
You can install this package from source or from PyPi.
$ pip install pypuppetdb$ git clone https://github.com/nedap/pypuppetdb
$ python setup.py installIf you wish to hack on it clone the repository but after that run:
$ pip install -r requirements.txtThis will install all the runtime requirements of pypuppetdb and the dependencies for the test suite and generation of documentation.
Once you have pypuppetdb installed you can configure it to connect to PuppetDB and take it from there.
The first thing you need to do is to connect with PuppetDB:
>>> from pypuppetdb import connect
>>> db = connect()The following will return a generator object yielding Node objects for every returned node from PuppetDB.
>>> nodes = db.nodes()
>>> for node in nodes:
>>> print(node)
host1
host2
...To query a single node the singular node() can be used:
>>> node = db.node('hostname')
>>> print(node)
hostnameThe Node objects are a bit more special in that they can query for facts and resources themselves. Using those methods from a node object will automatically add a query to the request scoping the request to the node.
>>> node = db.node('hostname')
>>> print(node.fact('osfamily'))
osfamily/hostname>>> facts = db.facts('osfamily')
>>> for fact in facts:
>>> print(fact)
osfamily/host1
osfamily/host2That queries PuppetDB for the 'osfamily' fact and will yield Fact objects, one per node this fact is known for.
>>> resources = db.resources('file')Will return a generator object containing all file resources you're managing across your infrastructure. This is probably a bad idea if you have a big number of nodes as the response will be huge.
This project is still very new so it's not inconceivable you'll run into issues.
For bug reports you can file an issue. If you need help with something feel free to hit up @daenney by e-mail or find him on IRC. He can usually be found on IRCnet and Freenode and idles in #puppet.
There's now also the #puppetboard channel on Freenode where we hang out and answer questions related to pypuppetdb and Puppetboard.
API documentation is automatically generated from the docstrings using Sphinx's autodoc feature.
Documentation will automatically be rebuilt on every push thanks to the Read The Docs webhook. You can find it here.
You can build the documentation manually by doing:
$ cd docs
$ make htmlDoing so will only work if you have Sphinx installed, which you can acheive through:
$ pip install -r requirements.txtWe welcome contributions to this library. However, there are a few ground rules contributors should be aware of.
This project is licensed under the Apache v2.0 License. As such, your contributions, once accepted, are automatically covered by this license.
Write decent commit messages. Don't use swear words and refrain from uninformative commit messages as 'fixed typo'.
The preferred format of a commit message:
docs/quickstart: Fixed a typo in the Nodes section. If needed, elaborate further on this commit. Feel free to write a complete blog post here if that helps us understand what this is all about. Fixes #4 and resolves #2.
If you'd like a more elaborate guide on how to write and format your commit messages have a look at this post by Tim Pope.
Commits are expected to contain tests or updates to tests if they add to or modify the current behaviour.
The test suite is powered by pytest and requires pytest, pytest-pep8, httpretty and pytest-httpretty which will be installed for you if you run:
$ pip install -r requirements.txtTo run the unit tests (the ones that don't require a live PuppetDB):
$ py.test -v -m unitIf the tests pass, you're golden. If not we'll have to figure out why and fix that. Feel free to ask for help on this.