puppetlabs/control-repo extended with not-so-core stuff https://git.pfeiffer.tech/control-repo-template/atom?h=1.1.0-lnde 2019-02-26T17:14:15Z 2019-02-26T17:14:15Z Reid Vandewiele reid@puppetlabs.com 2019-02-25T17:08:36Z urn:sha1:baa4b92a8801df4ad026da13b0e0bd68c5cbdd3a The symlink served for a good discussion point around change impact, but in the end having it makes for a more confusing experience overall both to new users cloning the control-repo to get started and also to anyone accustomed to "site". A new user won't miss "site". A symlink will muddy the waters over the change for long-time users. Better for clarity to be all-in and not include a symlink. 2019-02-04T21:04:11Z Nick Walker nick.walker@puppetlabs.com 2019-02-04T21:04:11Z urn:sha1:80494c198b07557713ae3d44811935fcd9b215da 2019-02-01T00:58:13Z Nick Walker nick.walker@puppetlabs.com 2019-02-01T00:58:13Z urn:sha1:ead7f3c706657bbfae37ff40c8f919fb57c8a841 Prior to this commit, we placed modules local to a users installation in the `site` directory. This was just a convention and the name `site` doesn't clearly convey what it is for. After this commit, we place modules local to a users installation in the `site-modules` directory. This makes it more clear to users that this is a directory that modules go i. When users start with bolt they won't even know what a control-repo is and renaming site to site-modules gives them a better idea of why they should put their modules with tasks in them. Also see: https://tickets.puppetlabs.com/browse/BOLT-1108 2016-06-14T04:37:43Z Dylan Ratcliffe dylan.ratcliffe@puppet.com 2016-06-14T04:37:43Z urn:sha1:aa2dba158b5433272acaa69dde43abb1d6cc200b 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 2016-03-24T21:07:16Z Nick Walker nick.walker@puppetlabs.com 2016-03-24T21:07:16Z urn:sha1:b3519dd48cebfcdbf1dea4b42e8857e21e6f05a2 Prior to this commit, there was a stash profile in the site dir of this control-repo. After this commit, the profile has been moved to it's own repo where it can be used more generally and not tightly coupled to this repository. 2016-03-24T15:27:17Z Nick Walker nick.walker@puppetlabs.com 2016-03-24T15:27:17Z urn:sha1:ff6f140529b646e09fb66952abfbe6fa7b4cc746 Prior to this commit, there was a gitlab profile in the site dir of this control-repo. After this commit, the profile has been moved to it's own repo where it can be used more generally and not tightly coupled to this repository. As a result, the gitlab role has been removed from this repository as well. 2016-03-23T22:55:58Z Nick Walker nick.walker@puppetlabs.com 2016-03-23T22:53:41Z urn:sha1:9503f54349756fe7a93eecf2ecc6620c340f4679 Prior to this commit, the puppetmaster profile was embedded in this control-repo. After this commit, the puppetmaster profile is moved out into its own module. 2016-03-23T17:22:02Z Nick Walker nick.walker@puppetlabs.com 2016-03-23T17:22:02Z urn:sha1:5185a4cb2691796953a5f22359cb91592af3ea6c Prior to this commit, these two files were laying around but not used. The code manager template was missed when the code was moved into a module and the function was added a while ago but then never put to use. After this commit, the codebase is a little lighter without these stale files. 2016-03-17T21:33:01Z Nick Walker nick.walker@puppetlabs.com 2016-02-25T23:23:12Z urn:sha1:00d3aa1f4f835a78e14827d5ac1ae9e94bc3f924 Prior to this commit the functionality to setup the either code manager or zack/r10k was tightly coupled to this control-repo. In an effort to make that functionality useful to more people we're splitting it into a dedicated module. After this commit, the pe_code_manager_webhook module will contain all logic around setting up the webhook while this control-repo will still gloss over the details needed to get everything in PE setup correctly to use that module. This commit removes the files associated with the profile including some custom functions that were only there to make it work. This commit removes the all_in_one_pe_2015_2 role as it was exactly the same as the all_in_one_pe role. This commit modifies all_in_one_pe to use the pe_code_manager_webhook module instead of the profile.