Currently, before XlineServer starts, we need to get information such as cluster_info and db, and these logics are scattered in the main and test cluster implementations, if these logics changed, we need to modify multiple locations, which is a very bad implementation, so we need to refactor the XlineServer startup logic and use the same sub-methods in all locations
Code of Conduct
[X] I agree to follow this project's Code of Conduct
Description about the feature
Currently, before XlineServer starts, we need to get information such as cluster_info and db, and these logics are scattered in the main and test cluster implementations, if these logics changed, we need to modify multiple locations, which is a very bad implementation, so we need to refactor the XlineServer startup logic and use the same sub-methods in all locations
Code of Conduct