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
Allow including a role if defined via a trusted fact on the node
during provisioning time. This is how I will bootstrap any
necessary configuration on the master, or other PE internal nodes.
Stole Gary's puppet_repository and modified it for general
general consumption.
Upped the version of r10k to newest (1.4.1)
Ripped out the hiera examples just left defaults.yaml
Tweaked environment.conf
