Summary

In this chapter, we have reviewed the tools that can help us from when we start to write our Puppet code, to how we manage, test, and deploy it.

We have seen how to enhance the writing experience on Geppetto, Puppet Labs' official Puppet IDE and Vim, a sysadmins' evergreen tool, how to version and manage code with Git, and eventually, how to introduce a peer review and approval system such as Gerrit.

We then saw the different tools and methodologies available to test our code: from simple syntax checks, which should be automated in Git hooks; to style checks with puppet-lint, from unit testing on modules with puppet-rspec; to real life acceptance tests on running (and ephemeral) Virtual Machines, managed with Vagrant; and using tools like Beaker.

We finally faced how Puppet code can be delivered to production, with tools such as librarian-puppet and r10k.

The execution of all these single tools can be automated with Continuous Integration tools, either to trigger tests automatically...