Skip to content

Update `User` to use `MainClusterwide::ApplicationRecord`

Manoj M J requested to merge 410374-cells-iteration-2-make-class-user-to-use-mainclusterwide-applicationrecord into master

What does this MR do and why?

Related to #410374 (closed)

We want the User model to inherit from MainClusterwide::ApplicationRecord, as we are building cells and the User model is marked as a clusterwide table.

Currently, this change has no effect, because MainClusterwide::ApplicationRecord only points to the main_clusterwide database for reading/writing only if that database is configured in database.yml, which we currently do not.

So, essentially, this change now acts as NO-OP.

This change also does not lead to cross-join failures or anything like that because all such areas are controlled via db/table.yml files now, and we there have gitlab_schema defined for users in users.yml and it points to main_clusterwide already.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #410374 (closed)

Edited by Manoj M J

Merge request reports