Add FDW schema refresh to Geo rake task and refactor some code
What does this MR do?
- Add refresh foreign tables tasks to Geo rake tasks
- Extract some code out of Geo rake tasks into it's own Helper class
When in a source install, user will have to invoke the rake task by itself during the installation process. When in an Omnibus GitLab install, this will be triggered automatically.
Are there points in the code the reviewer needs to double check?
Why was this MR needed?
Missing bit from omnibus-gitlab#2760 (closed)
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated (gitlab-org/gitlab-ee!3076) -
API support added -
Tests added for this feature/bug - Review
-
Has been reviewed by UX -
Has been reviewed by Frontend -
Has been reviewed by Backend -
Has been reviewed by Database
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Squashed related commits together -
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
What are the relevant issue numbers?
Edited by Gabriel Mazetto