control-repo-template - puppetlabs/control-repo extended with not-so-core stuff

	Commit message (Collapse)	Author	Age	Files	Lines
*	Enable Hiera 5	Reid Vandewiele	2017-11-15	1	-1/+0
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	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/ => 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.
*	Reduce the scope of the control-repo to mostly an example	Nick Walker	2016-03-29	1	-0/+1
	Prior to this commit, the control-repo was an example of the structure of a control repo but it also included puppet code to help setup code manager and instructions to get that all setup in a very specific way. This was great for users that wanted to follow those instructions exactly but wasn't great for people just looking for an example to start from. After this commit, the control-repo will be just an example once again and a new repo somehwere else will pop up to provide the explicit instructions on how to use the example with code manager. There are links added to puppetlabs/control-repo to a new repo that will have a version of the code that once lived in puppetlabs/control-repo