Book Image

Puppet 8 for DevOps Engineers

By : David Sandilands
Book Image

Puppet 8 for DevOps Engineers

By: David Sandilands

Overview of this book

As DevOps and platform engineering drive the demand for robust internal development platforms, the need for infrastructure configuration tools has never been greater. Puppet, a powerful configuration management tool, is widely used by leading enterprises and boasts a thriving open source community. This book provides a comprehensive explanation of both the Puppet language and the platform. It begins by helping you grasp the basic concepts and approach of Puppet as a stateful language, and then builds up to explaining how to structure Puppet code to scale and allow flexibility and collaboration among teams. As you advance, you’ll find out how the Puppet platform allows the management and reporting of infrastructure configuration. The book also shows you how the platform can be integrated with other tooling, such as ServiceNow and Splunk. The concluding chapters help you implement Puppet to fit in heavily regulated and audited environments as well as modern hybrid cloud environments. By the end of this book, you’ll have gained a solid understanding of the capabilities of both the Puppet language and platform, and you will have learned how to structure and scale Puppet to create a platform to provide enterprise-grade infrastructure configuration.
Table of Contents (22 chapters)
1
Part 1 – Introduction to Puppet and the Basics of the Puppet Language
7
Part 2 – Structuring, Ordering, and Managing Data in the Puppet Language
12
Part 3 – The Puppet Platform and Bolt Orchestration
17
Part 4 – Puppet Enterprise and Approaches to the Adoption of Puppet

Understanding the structure of projects

A Bolt project is a simple directory structure providing configuration and data for Bolt to use. Within this structure, Puppet modules from both Forge and private repositories can be stored along with task plans and policies. Bolt identifies a directory as a Bolt project if a bolt-project.yaml file exists in it, and this file contains a name key. To create this file, run bolt project init for Unix systems or New-BoltProject for PowerShell from within a directory in which you wish to add Bolt project files. This will use the name for the project as the name of the directory, but you can override this by running it with a name using the bolt project init customname or New-BoltProject -Name customname command, for Unix systems and PowerShell, respectively.

This project name must start with a lowercase letter and can only use lowercase letters, digits, and underscores. This is because Bolt projects are like modules and get loaded into the module...