What does this MR do?
Dynamically sets the database connection for
Are there points in the code the reviewer needs to double check?
Is there a better approach to dynamically set the database connection?
Why was this MR needed?
Gitlab::Geo.secondary? changes on primary, we need to reinitialize the connection properly in the model to avoid requiring a full unicorn restart on secondary.
Does this MR meet the acceptance criteria?
Changelog entry added, if necessary
API support added
Added for this feature/bug
All builds are passing
Conform by the merge request performance guides
Conform by the style guides
Branch has no merge conflicts with
master(if it does - rebase it please)
Squashed related commits together
What are the relevant issue numbers?
Closes #2181 (closed)