Automatically define DB generation jobs from listed db connections
Overview
@ysiev spotted that attempting to disable the gitlab.rails.databases.sec.use_main_database setting in the GDK results in the following issue when attempting to reconfigure the GDK:
rake dev:copy_db:sec
Don't know how to build task 'dev:copy_db:sec' (See the list of available tasks with `rake --tasks`)
Did you mean? dev:copy_db:ciThis was mentioned as a one of the one off solutions done for the CI decompsotion that we wish to resolve more sustainably this time around by defining these jobs dynamically from the defined DB connections in db/database_connections. (There is a class that relies one these that we can tap into in the Rake job definitions.
Impacted categories
The following categories relate to this issue:
-
gdk-reliability - e.g. When a GDK action fails to complete. -
gdk-usability - e.g. Improvements or suggestions around how the GDK functions. -
gdk-performance - e.g. When a GDK action is slow or times out.