Volunteers to run `gitlab.rails.databases.ci.use_main_database=false` (separate database) on GDK

GDK by default now uses multiple database connections but using the same database.

We now wish to make these database connections use separate main:, and ci: databases. This is in preparation for GitLab.com being the same.

To help discover potential issues, we are looking for volunteers to test this out.

1. Fill in your name, and role in the table below.

2. Run the following to configure separate databases:

   $ gdk config set gitlab.rails.databases.ci.use_main_database false
   $ gdk reconfigure

3. Create the new database gitlabhq_development_ci (†) by copying from gitlabhq_development. Open gdk psql, then run: gdk reconfigure will now create this database for you.

   CREATE DATABASE gitlabhq_development_ci WITH TEMPLATE gitlabhq_development;

4. Report back to this issue with your findings after a week.

• † Note: All CI data will be stored in this database from now on. See also FAQ

We are looking for a diverse set of people who use GDK to volunteer for this:

Name	Role
@tkuah	Staff Backend Engineer, Sharding
@marc_shaw	Backend Engineer, Code Review, Create
@dcouture	Staff Security Engineer, Application Security
@ashmckenzie	Staff Backend Engineer, EP
@mbobin	Senior Backend Engineer, Verify, PE
@pgascouvaillancourt	Senior Frontend Engineer, Secure:Threat Insights
@alberts-gitlab	Senior Backend Engineer, Verify, Pipeline Insights
@ekigbo	Senior Frontend Engineer, Manage, Optimize
@OmarQunsulGitlab	Backend Engineer, Sharding
cell	cell
cell	cell

Note: all engineers in @gitlab-org/sharding-group have been developing locally with decomposed databases for the last 6 months.

Reporting back your experience

When posting your report / question:

1. Make sure to include the contents of your gdk.yml, and gitlab/config/database.yml files

FAQ / Troubleshooting

See #356349 (closed)