<feed xmlns='http://www.w3.org/2005/Atom'>
<title>control-repo-template/data/nodes, branch 1.1.0-lnde</title>
<subtitle>puppetlabs/control-repo extended with not-so-core stuff</subtitle>
<id>https://git.pfeiffer.tech/control-repo-template/atom?h=1.1.0-lnde</id>
<link rel='self' href='https://git.pfeiffer.tech/control-repo-template/atom?h=1.1.0-lnde'/>
<link rel='alternate' type='text/html' href='https://git.pfeiffer.tech/control-repo-template/'/>
<updated>2017-11-15T17:24:40Z</updated>
<entry>
<title>Enable Hiera 5</title>
<updated>2017-11-15T17:24:40Z</updated>
<author>
<name>Reid Vandewiele</name>
<email>reid@puppetlabs.com</email>
</author>
<published>2017-11-15T17:24:40Z</published>
<link rel='alternate' type='text/html' href='https://git.pfeiffer.tech/control-repo-template/commit/?id=7264b63d10ca828aff611d94aa730cc5451a7a5c'/>
<id>urn:sha1:7264b63d10ca828aff611d94aa730cc5451a7a5c</id>
<content type='text'>
This commit enables the control repo to use Hiera 5 environment-level
hiera hierarchy. This means adding a hiera.yaml to the repo, and moving
hieradata/ =&gt; data/.

We should do this to the control-repo template new customers base off of
because in a Hiera 5 world, the global hiera.yaml should be very minimal
(possibly even ONLY having the console level), and everything else
(nodes, common) belongs in the environment hiera.yaml.

This control-repo template is how people start using Puppet. It should
reflect using our most modern technologies.
</content>
</entry>
</feed>
