control-repo-template/manifests, branch 1.1.0-lnde puppetlabs/control-repo extended with not-so-core stuff https://git.pfeiffer.tech/control-repo-template/atom?h=1.1.0-lnde 2019-05-06T22:36:50Z Update outdated info and links in site.pp comments 2019-05-06T22:36:50Z Nate McCurdy mccurdy.nate@gmail.com 2019-05-06T22:31:50Z urn:sha1:a8c6d51264bf5e9d8526283a64d29d0b1f7c16e2 This commit attempts to cleanup and modernize the comments in site.pp a bit. For one thing, I've updated the docs links to point to working URL's. For another, I tried to reorganize, clarify, and deduplicate the comments. Provide permalink for filebucket deprecation (#43) 2016-10-26T14:46:56Z Alex Harden aharden@gmail.com 2016-10-26T14:46:56Z urn:sha1:b6af290069f6ff5bba64ba63e983964c44ccae84 "Latest" stopped resolving several PE releases ago. Reduce the scope of the control-repo to mostly an example 2016-03-29T22:53:10Z Nick Walker nick.walker@puppetlabs.com 2016-03-23T17:31:33Z urn:sha1:2c98a9264c2070281dc7628d5bcb176eb0fdb200 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 Disable file bucket to match default PE2015.3 behavior 2015-12-18T17:24:27Z Nick Walker nick.walker@puppetlabs.com 2015-12-07T16:03:13Z urn:sha1:2ed03892d9c9205cc3d5b624c648e4dca9e5b2b6 Merge branch 'production' of https://github.com/npwalker/control-repo into merge_npwalker_control_repo 2015-11-24T19:16:51Z Nick Walker nick.walker@puppetlabs.com 2015-11-24T19:16:51Z urn:sha1:afc9a358f30c51029d7a37122d4adfcc2add88a6 fix incorrect curly brace 2015-10-22T21:25:17Z Nick Walker nick.walker@puppetlabs.com 2015-10-22T21:25:17Z urn:sha1:86cb66b057c0d2c45519f0cdceb28206528c7e1b fix site.pp to not include a role that is empty 2015-10-22T21:15:13Z Nick Walker nick.walker@puppetlabs.com 2015-10-22T21:15:13Z urn:sha1:9d1b750d743a4060101949de41838fec61985862 Add a site.pp 2015-08-25T21:19:29Z Nick Walker nick.walker@puppetlabs.com 2015-08-25T19:21:30Z urn:sha1:2e457d5c0ee8c8008bde68b6abd1b8b2fe2a6911 I needed to modify the site.pp to use $servername so it would work out of the box and that is the closest thing to the current behavior. Fix some quoting issues and add role:: to the include in site.pp 2015-08-13T22:41:11Z Nick Walker nick.walker@puppetlabs.com 2015-08-13T22:41:11Z urn:sha1:70690333eedbb28b3f286912e6d9749b4a7e2618 Update site.pp to use a trusted fact role 2015-08-04T00:24:41Z Nick Walker nick.walker@puppetlabs.com 2015-08-04T00:24:41Z urn:sha1:921c83736ee9ec1ff48d3e18137292bb38829262 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.