fix(datastore): do not panic if database credentials are wrong

added Category:Container Registry backend database devopspackage golang grouppackage registry typebug workflowscheduling labels

added sectionops label

set weight to 1

added workflowready for development label and removed workflowscheduling label

added [deprecated] good for new contributors label

changed title from Fix panic when database credentials are wrong to fix(datastore): do not panic if database credentials are wrong

added priority2 label

changed the description

changed milestone to %14.5

added Package:P2 Stretch labels

mentioned in issue gitlab#341294 (closed)

mentioned in issue gitlab-org/ci-cd/package-stage/onboarding#11 (closed)

assigned to @jaime

changed milestone to %14.6

Starting on this issue this week 😄

added workflowin dev label and removed workflowready for development label

@jdrpereira do we still want to fail to start or should we keep running but disable the datastore (and print a warning)?

@jaime, as a general rule of thumb, if a user/admin requested a feature to be enabled, then we should fail to start if we can't setup/verify the pre-requisites for that feature.

In this specific case, we should definitely fail as soon as possible, otherwise, this could lead to data inconsistencies or at least unavailability for repositories stored in the database.