Book Image

Puppet 5 Essentials - Third Edition

By : Martin Alfke, Felix Frank
Book Image

Puppet 5 Essentials - Third Edition

By: Martin Alfke, Felix Frank

Overview of this book

Puppet is a configuration management tool that allows you to automate all your IT configurations, giving you control over what you do to each Puppet Agent in a network, and when and how you do it. In this age of digital delivery and ubiquitous Internet presence, it's becoming increasingly important to implement scaleable and portable solutions, not only in terms of software, but also the system that runs it. This book gets you started quickly with Puppet and its tools in the right way. It highlights improvements in Puppet and provides solutions for upgrading. It starts with a quick introduction to Puppet in order to quickly get your IT automation platform in place. Then you learn about the Puppet Agent and its installation and configuration along with Puppet Server and its scaling options. The book adopts an innovative structure and approach, and Puppet is explained with flexible use cases that empower you to manage complex infrastructures easily. Finally, the book will take readers through Puppet and its companion tools such as Facter, Hiera, and R10k and how to make use of tool chains.
Table of Contents (10 chapters)

Managing file snippets

The next technique that we are going to discuss helps you solve conflicts in your manifests and build some elegant solutions in special situations. This mostly refers to configuration files where one is either not able to manage the whole file or where a file is constructed from different subclasses.

Puppet offers several ways to accomplish this:

  • Single line
  • Single entry in a section
  • Building from multiple snippets
  • Other resource types

How do you deal with a configuration file, where a user may add additional content? What we have seen so far is management of complete configuration files, where changes will get reset. But think about the users .bashrc file, where the system administrator wants to ensure that the user is making use of a specific proxy.

Normally, one can specify this globally in a /etc/profile.d/ snippet. This is more meant to be a showcase...