Reduce the scope of the control-repo to mostly an example

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

1 files changed, 0 insertions, 8 deletions

diff --git a/manifests/site.pp b/manifests/site.pp
index 04b3d6e..5573ee0 100644
--- a/manifests/site.pp
+++ b/manifests/site.pp
@@ -26,14 +26,6 @@ File { backup => false }
 # specified in the console for that node.
 
 node default {
-  #incude a role on any node that specifies it's role via a trusted fact at provision time
-  #https://docs.puppetlabs.com/puppet/latest/reference/lang_facts_and_builtin_vars.html#trusted-facts
-  #https://docs.puppetlabs.com/puppet/latest/reference/ssl_attributes_extensions.html#aws-attributes-and-extensions-population-example
-
-  if !empty( $trusted['extensions']['pp_role'] ) {
-    include "role::${trusted['extensions']['pp_role']}"
-  }
-
   # This is where you can declare classes for all nodes.
   # Example:
   #   class { 'my_class': }