Store template congregate.conf file to avoid requiring congregate configure
Overview
As a first step to addressing gitlab-com/customer-success/professional-services-group/global-practice-development/migration/congregate#405, a template config file should be stored in the repo describing what each configuration option does and how it is used.
Refer to how the gitlab.rb.template is written
Tasks
-
Create a congregate.conf.template
file at the root of the repo -
Store every config listed in conf.py with an example setting -
Comment out every line so nothing is accidentally used -
Provide a description of what each configuration setting does or refer to the conf.py file -
Update docs if needed (workflow, runbooks, README, migration metrics, etc.)
Acceptance Criteria
-
Existing UTs pass locally -
100% code coverage on new code
Weight estimation
@leopardm @pprokic @mlindsay @nicki_peric @bryan-may @ctimberlake1 @sfirdaus @dtacheny
Please leave your weight estimation as a reaction to this issue (reference). The final weight will be one level higher than the majority weight.
Edited by S A Firdaus