control-repo-template/Puppetfile, branch productionpuppetlabs/control-repo extended with not-so-core stuffhttps://git.pfeiffer.tech/control-repo-template/atom?h=production2021-05-04T13:11:43Zupdate the version of the example modules2021-05-04T13:11:43ZEdwin Maldonadomckain.default@gmail.com2021-05-04T13:11:43Zurn:sha1:33ee3da468a9f5b736329e200b3378f2705e4a68Revert "add db2 module"2019-12-03T19:35:22ZIristyleIristyle@github2019-12-03T19:16:46Zurn:sha1:882089207ccc0f326007c0dbdb415426f6e100f2
This reverts commit bfb2d7a1828b22f7f7e5d4955743ccd9f08147db.
add db2 module2019-11-29T22:22:07ZJesse Reynoldsjesse@va.com.au2019-11-29T22:22:07Zurn:sha1:bfb2d7a1828b22f7f7e5d4955743ccd9f08147db(maint) Update Puppetfile versions, update style2019-07-11T16:33:14ZReid Vandewielereid@puppetlabs.com2019-07-10T18:22:04Zurn:sha1:dddbd8d15c0f8432c8dbb512c74c45eae312fc32
This commit updates the Puppetfile example module versions to list the
latest releases for the example modules as of 2019-07-10, and also
updates several files for style.
Standardizing on double-quotes in YAML due to:
1. Functional irrelevance between single vs. double quotes in our YAML
2. Prevalent use of double-quotes in Puppet documentation
3. Similar look-and-feel to other data serialization formats like JSON
Update module examples to latest versions2018-05-08T17:46:30ZNate McCurdynate.mccurdy@puppet.com2018-05-08T17:41:44Zurn:sha1:f69ffd8ce1a995892c7bca84d8c67e0c1a39a47eResolve Rubocop warnings2018-05-08T17:46:30ZNate McCurdynate.mccurdy@puppet.com2018-05-08T17:37:30Zurn:sha1:36a278427582e6629141eb8539f658cf1604a528
* Removed the useless assignment in the config_version.rb error catching
* Single quote vs. double quote in Puppetfile
point "forge" to new canonical URL, with https2017-11-27T20:41:11ZIgor Galići.galic@brainsware.org2017-11-27T20:41:11Zurn:sha1:9a13af11c6db7a1b10aa2b75418e551436f2daaaReduce the scope of the control-repo to mostly an example2016-03-29T22:53:10ZNick Walkernick.walker@puppetlabs.com2016-03-23T17:31:33Zurn: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
Move stash profile out to its own 'profile' module2016-03-24T21:07:16ZNick Walkernick.walker@puppetlabs.com2016-03-24T21:07:16Zurn: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.
Move gitlab profile out to its own 'profile' module2016-03-24T15:27:17ZNick Walkernick.walker@puppetlabs.com2016-03-24T15:27:17Zurn: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.