| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Add functionality to disable the zack/r10k webhook | Nick Walker | 2015-12-21 | 1 | -0/+14 |
| | | | | | | | | | | | | Prior to this commit, if you upgraded from a previous version of the control-repo both code manager and zack/r10k webhook would be running and ready to receive data. This can present problems if the webhook isn't disbled in the git management system is sending data to both receivers. This commit adds rudimentary ability to break the zack/r10k webhook so it can't receive data. | ||||
| * | Create profile::git_webhook to abstract away the details | Nick Walker | 2015-12-21 | 2 | -0/+186 |
| 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. | |||||
