git.lirion.de

Of git, get, and gud

	Commit message (Collapse)	Author	Age	Files	Lines
*	Revert "add db2_server role and profile"	Iristyle	2019-12-03	1	-4/+0
\| \| \| \|	This reverts commit 58103e4ef4478f7c997c769a7111ca48cdf269eb.
*	add db2_server role and profile	Jesse Reynolds	2019-11-30	1	-0/+4
\|
*	Rename site directory to site-modules	Nick Walker	2019-01-31	3	-0/+17
	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

away the detailsNick Walker 2015-12-211-1/+1 | | | | | | | | | | | | | Prior to this commit there were two possible webhooks - zack/r10k webhook - code manager I moved these two profiles under git_webhook and choose the correct one based on the version of PE being used. As a safety hatch, I provide the $force_zack_r10k_webhook param on profile::git_webhook in case someone needs to continue using it instead of code manager. * Final steps to make Code Manager workNick Walker 2015-12-182-1/+6 | | | | | | | | | | - Moved ssh key generation and git deploy key out of the puppetmaster profile and into zack_r10k and code_manager - Swapped code manager into the all_in_one role - Made a 2015.2 all_in_one role if users prefer to use it - Conditionally move all existing code out of environmentpath to allow file sync to sync files - Update the README to compliment the new puppet code * Refactor puppetmaster and zack_r10k_webhookNick Walker 2015-12-091-12/+3 | | | | | | | | | | Moved the webhook resource out of puppetmaster and into zack_r10k to support exchaning code_manager in place of zack_r10k As a result I cleaned up some unnecessary parameters. Installing both the r10k webhook and the code_manager at this time for testing * Merge branch 'production' of https://github.com/npwalker/control-repo into ↵Nick Walker 2015-11-244-0/+35 |\ | | | | | | merge_npwalker_control_repo | * fixing a bunch of puppet lint warningsNick Walker 2015-10-301-1/+1 | | | * Refactor webhook profiles into one profile with a parameterNick Walker 2015-10-301-1/+1 | | | | | | | | | | | | | | | | Previously there was a mcollective and no_mcollective version of the webhook profile. They were almost identical so I merged them and manage the difference with a "use_mcollective" parameter. I renamed the webhook profile to zack_r10k_webhook. | * Change the zack/r10k webhook to utilize username and passwordNick Walker 2015-10-301-2/+12 | | | | | | | | | | | | | | To accomodate generating random usernames and passwords, I had to parameterize the profiles which I didn't feel great about but I also didn't want to have to put the username and pass in hiera. | * Change to using the webhook without mcollectiveNick Walker 2015-10-161-0/+1 | | | | | | | | | | | | In order to complete the change I refactered the webhook into its own set of profiles, one with mcollective and the other without. | * Add a gitlab roleNick Walker 2015-08-141-0/+5 | | | * Update the README, add an all_in_one_pe roleNick Walker 2015-08-131-0/+5 | | | | | | | | | | | | | | | | | | | | | | Updating README for instructions on how to use the control-repo by putting it in your own git server and then using the r10k answers during installation of PE. Removing the manifest for configuring r10k using zack/r10k. Added a role that can be used to bootstrap an all-in-one PE installation. | * Add a site directory with example role and profile moduleNick Walker 2015-05-272-0/+14 | * add example files to role and profile directoriesNick Walker 2015-08-251-0/+3