moved readonly request logic into EE module
What does this MR do?
Since a read only database is only ever used in Geo, let's move the logic that limits requests when using a read only database into EE. This saves CE from the additional overhead, and allow EE specific requests (ala Geo) to be added easily.
Are there points in the code the reviewer needs to double check?
Why was this MR needed?
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
-
Changelog entry -
Documentation created/updated -
API support added -
Tests added for this feature/bug - Conform by the code review guidelines
-
Has been reviewed by a UX Designer -
Has been reviewed by a Frontend maintainer -
Has been reviewed by a Backend maintainer -
Has been reviewed by a Database specialist
-
-
EE specific content should be in the top level /ee
folder -
Conform by the merge request performance guides -
Conform by the style guides -
Conform by the database guides -
If you have multiple commits, please combine them into a few logically organized commits by squashing them -
Internationalization required/considered -
If paid feature, have we considered GitLab.com plan and how it works for groups and is there a design for promoting it to users who aren't on the correct plan -
End-to-end tests pass ( package-and-qa
manual pipeline job)
What are the relevant issue numbers?
CE MR: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/20414
Needed for: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/6248