Geo: Leverage Rails 6 features to manage multiple databases
Proposal
This needs subissues, in particular since it needs changes to omnibus-gitlab and charts.
-
Configure tracking database in database.yml
instead of customdatabase_geo.yml
-
Use connects_to
to make Geo models use the tracking database instead ofdef self.connection
override inGeo::TrackingBase
-
Use connected_to
block to manually use the tracking database instead ofGitlab::Geo::DatabaseTasks#set_db_env
-
Deprecate custom rake geo:db:*
rake tasks in favor of built-in tasksrake db:*:geo