Geo: order of steps in docs is important
What does this MR do?
Make it clearer that database replication needs to be complete before proceeding to other steps.
Are there points in the code the reviewer needs to double check?
Why was this MR needed?
A customer tried to configure geo without first configuring replication.
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
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
What are the relevant issue numbers?
Edited by 🤖 GitLab Bot 🤖