Opened on 11/14/2016 at 11:29:38 AM
#4640 new change
Move Mercurial repository configuration to Puppet
| Reported by: | trev | Assignee: | |
|---|---|---|---|
| Priority: | Unknown | Milestone: | |
| Module: | Infrastructure | Keywords: | |
| Cc: | matze | Blocked By: | |
| Blocking: | Platform: | Unknown / Cross platform | |
| Ready: | no | Confidential: | no |
| Tester: | Unknown | Verified working: | no |
| Review URL(s): | |||
Description
Background
Currently, the repositories on hg1 are being created and configured manually. This is unnecessarily error-prone.
What to change
Move repository configuration into modules/private/hiera/roles/hgwebserver.yaml. Something along these lines:
hgweb::repositories:
adblockplus:
contact: "Wladimir Palant <trev@adblockplus.org>"
description: "Adblock Plus for Firefox source code"
github_push: yes
irc: yes
sitescripts:
...
legacy_push: yes
foobar:
...
denyweb: yes
.hg/hgrc files for the Mercurial repositories should be generated by Puppet, the keys contact, description, github_push, legacy_push, irc and denyweb should be sufficient for that. If a repository directory doesn't exist yet or doesn't have an .hg directory Puppet should run hg init on it. So creating new repositories should be a matter of adding them to the hgwebserver.yaml file and deploying.
