Cells: Iteration 2: Configure `users` adjacent tables to be `gitlab_main_clusterwide` to support `User can create Group`
Problem
As part of the #404762 (comment 1342204543)+ a set of tables were identified as belong to clusterwide. Those tables were touched when trying to execute workflow User can create group.
Proposal
- Assign all below tables to
gitlab_main_clusterwide
. - Identify all cross-joins violations and define which ones should be solved to support this workflow.
- Each of those database models should use
< MainClusterwide::ApplicationRecord
Tables
-
appearances- this is alreadymain_clusterwide
- chat_teams
- emails
- gitlab_subscriptions
- identities
-
licenses- this is alreadymain_clusterwide
- notification_settings
- plans
- redirect_routes - hard?
- routes - hard?
- saml_providers
- upcoming_reconciliations
- user_callouts
- user_details
- user_group_callouts
- user_preferences
- user_statuses
- user_synced_attributes_metadata
UPDATE after the work was completed in this issue:
We merged updates with !127719 (merged), in which the following tables were classified as main_clusterwide
- emails
- identities
- plans
- routes
- redirect_routes
- user_callouts
- user_details
- user_preferences
- user_statuses
- user_synced_attributes_metadata
Other tables from the preliminary list above were classified to be main_cell
and will be migrated in #415204 (closed)
Edited by Manoj M J