Extract ClusterTopicManipulationService out of SingleClusterMonitor such that it can be instantiated as a separate service

Extract ClusterTopicManipulationService out of SingleClusterMonitor such that it can be instantiated as a separate service rather than part of the SingleClusterMonitor App

Signed-off-by: Andrew Choi <[email protected]>

Author: Andrew Choi

src/main/java/com/linkedin/xinfra/monitor/apps/SingleClusterMonitor.java

@@ -10,7 +10,6 @@
 
 package com.linkedin.xinfra.monitor.apps;
 
-import com.linkedin.xinfra.monitor.services.ClusterTopicManipulationServiceFactory;
 import com.linkedin.xinfra.monitor.services.ConsumeService;
 import com.linkedin.xinfra.monitor.services.ConsumerFactory;
 import com.linkedin.xinfra.monitor.services.ConsumerFactoryImpl;
@@ -68,13 +67,11 @@ public SingleClusterMonitor(Map<String, Object> props, String name) throws Excep
 
     ProduceService produceService = new ProduceService(props, name);
     ConsumeService consumeService = new ConsumeService(name, topicPartitionResult, consumerFactory);
-    Service clusterTopicManipulationService = new ClusterTopicManipulationServiceFactory(props, name).createService();
 
     _allServices = new ArrayList<>(SERVICES_INITIAL_CAPACITY);
     _allServices.add(_topicManagementService);
     _allServices.add(produceService);
     _allServices.add(consumeService);
-    _allServices.add(clusterTopicManipulationService);
   }
 
   @Override