Expose `db_database_tasks` attribute
What does this MR do?
This attribute configures if database should be managed
by db.rake
tasks. This is not desired for additional databases
if they point to exactly the same main:
database
as this causes a troubles when provisioning or migrating.
The default is database_tasks: true
, but if Omnibus detect
that host/port/database equals to main it will automatically
set it to false
.
If the host is not equal, but still points to the same database
admin should configure database_tasks: false
by themselves.
Disclaimer: The presence of the Backport was merged.database_tasks:
without a backport (gitlab!82902 (merged)) is no-op, so it is safe.
Related issues
Checklist
See Definition of done.
For anything in this list which will not be completed, please provide a reason in the MR discussion
Required
-
Merge Request Title, and Description are up to date, accurate, and descriptive -
MR targeting the appropriate branch -
MR has a green pipeline on GitLab.com -
Pipeline is green on dev.gitlab.org if the change is touching anything besides documentation or internal cookbooks -
trigger-package
has a green pipeline running against latest commit
Expected (please provide an explanation if not completing)
-
Test plan indicating conditions for success has been posted and passes -
Documentation created/updated -
Tests added -
Integration tests added to GitLab QA -
Equivalent MR/issue for the GitLab Chart opened
Edited by Kamil Trzciński (Back 2025-01-01)