git.lirion.de

Of git, get, and gud

aboutsummaryrefslogtreecommitdiffstats
path: root/data
Commit message (Collapse)AuthorAgeFilesLines
* Enable Hiera 5Reid Vandewiele 2017-11-152-0/+3
This commit enables the control repo to use Hiera 5 environment-level hiera hierarchy. This means adding a hiera.yaml to the repo, and moving hieradata/ => data/. We should do this to the control-repo template new customers base off of because in a Hiera 5 world, the global hiera.yaml should be very minimal (possibly even ONLY having the console level), and everything else (nodes, common) belongs in the environment hiera.yaml. This control-repo template is how people start using Puppet. It should reflect using our most modern technologies.
© 2014-2019 lirion.de – served by cgit – All Rights Reverse Engineered
9b704a306bbcc0c02'>Merge pull request #65 from smortex/portability-fixesReid Vandewiele 2019-10-183-9/+32 |\ | | | | Improve portability | * Don't assume git is in /usr/bin; expect it on PATHReid Vandewiele 2019-10-161-2/+2 | | | * Restore and clarify config_version functionalityReid Vandewiele 2019-10-163-5/+52 | | | | | | | | | | | | | | | | This branch is intended as a portability fix. Some functionailty had been inadvertently removed as unused, but testing revealed that it had a purpose. Because the purpose was unclear, this commit restores the functionality AND clarifies it in the script names and comments in config_version.sh. | * Remove code dead for more than 2 yearsRomain Tartière 2018-05-112-30/+1 | | | | | | | | | | | | r10k generates a .r10k-deploy.json file since version 2.1.0 which was released on October 28, 2015. New users of the control-repo are not likely to have a so old version of r10k, so remove this dead code. | * Do sanity checking earlyRomain Tartière 2018-05-111-0/+5 | | | | | | | | Fail before doing anything when passed parameters are invalid. | * Remove execute permission and shebangsRomain Tartière 2018-05-112-2/+0 | | | | | | | | | | | | | | The appropriate ruby interpreter is determined by the config_version.sh shell script which explicitely use it to start these ruby scripts. Removing the execute bit ensure users will not run these script with the wrong Ruby version. | * Improve portabilityRomain Tartière 2018-05-111-11/+13 | | | | | | | | | | | | | | | | | | - Fix shebang: `bash` is not always in `/bin/`, and since the script does not have bashism, rely on `sh` which is always in `/bin/`; - Use `/opt/puppetlabs/puppet/bin/ruby` if this file exist and is executable, otherwise use `ruby` from $PATH; - Use `code_manager_config_version.rb` if `.r10k-deploy.json` is found, and `config_version.rb` in all other cases. * | Create CODEOWNERSBen Ford 2019-08-211-0/+1 | | * | (maint) Update Puppetfile versions, update styleReid Vandewiele 2019-07-113-11/+11 | | | | | | | | | | | | | | | | | | | | | | | | 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 * | Merge pull request #73 from natemccurdy/site_pp_updatesadam buxton 2019-05-141-14/+13 |\ \ | | | | | | Update outdated info and links in site.pp comments | * | Update outdated info and links in site.pp commentsNate McCurdy 2019-05-061-14/+13 |/ / | | | | | | | | | | | | | | 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. * | Merge pull request #71 from npwalker/rename_site_to_site-modules1.1.0Reid Vandewiele 2019-02-267-5/+5 |\ \ | | | | | | Rename site directory to site-modules | * | Update README to reflect site -> site-modulesReid Vandewiele 2019-02-261-4/+4 | | | | * | Remove symlink site -> site-modulesReid Vandewiele 2019-02-261-1/+0 | | | | | | | | | | | | | | | | | | | | | | | | | | | 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. | * | Add symlink from site to site-modules for compatibility