Ability to override db connection and other settings for gitlab CI

[sharique]

Currently the settings file path is hardcoded to load from vendor folder (vendor/mikemadison13/blt-gitlab-pipelines/settings/gitlab.settings.php). It should be able to load from settings folder.

[mikemadison13]

This move was intentional to be inline with how BLT handles this for Acquia Pipelines (see https://github.com/acquia/blt/blob/main/settings/pipelines.settings.php). This isn't something that gets moved into the settings folder, it's something that is just in the plugin.

Is there a reason why it should be in settings?

[sharique]

What I need to the ability override the db connection settings (settings folder is idea place), if somebody using different db.

Recently I was doing a small POC, where I was using Postgres DB in local, but I've use MySql in gitlab CI, as I didn't fine a way override db settings.

It will be good if we can have documentation on how to override db and other settings, may be I should create a separate ticket for it.