Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Puppet 4.10 Beginner???s Guide, Second Edition

You're reading from   Puppet 4.10 Beginner???s Guide, Second Edition From newbie to pro with Puppet 4.10

Arrow left icon
Product type Paperback
Published in May 2017
Publisher Packt
ISBN-13 9781787124004
Length 268 pages
Edition 2nd Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
John Arundel John Arundel
Author Profile Icon John Arundel
John Arundel
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Preface 1. Getting started with Puppet FREE CHAPTER 2. Creating your first manifests 3. Managing your Puppet code with Git 4. Understanding Puppet resources 5. Variables, expressions, and facts 6. Managing data with Hiera 7. Mastering modules 8. Classes, roles, and profiles 9. Managing files with templates 10. Controlling containers 11. Orchestrating cloud resources 12. Putting it all together Index

Setting up Hiera


Hiera needs to know one or two things before you can start using it, which are specified in the Hiera configuration file, usually named hiera.yaml (not to be confused with Hiera data files, which are also YAML files; we'll find about those later in this chapter). Each Puppet environment has its own local Hiera config file, located at the root of the environments directory (for example, for the production environment, the local Hiera config file would be /etc/puppetlabs/code/environments/production/hiera.yaml).

Tip

Hiera can also use a global config file located at /etc/puppetlabs/puppet/hiera.yaml, which takes precedence over the per-environment file, but the Puppet documentation recommends you only use this config layer for certain exceptional purposes, such as temporary overrides; all your normal Hiera data and configuration should live in the environment layer.

The following example shows a minimal hiera.yaml file (hiera_minimal.config.yaml):

---
version: 5

defaults:
  datadir...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime