Adding ITopicsRepository Interface

Type of change

• Refactoring

Please provide link to gitlab issue or ADR(Architecture Decision Record) #14 (closed)

Does this introduce a change in the core logic?

• [YES]

Does this introduce a change in the cloud provider implementation, if so which cloud?

• AWS
• Azure
• GCP
• IBM

Does this introduce a breaking change?

• [NO]

What is the current behavior?

Currently there is no SPI to implement for TopicsRepository

What is the new/expected behavior?

Adding ITopicsRepository Interface, CSP's can implement this interface to override the logic for reading the topic names

If any CSP wish not to implement this interface then also things will continue to work since TopicRepository in register core is already implementing the same

Gitlab Issue Link

Have you added/updated Unit Tests and Integration Tests?

Any other useful information

register-core/src/main/java/org/opengroup/osdu/register/provider/interfaces/subscriber/ITopicsRepository.java

+package org.opengroup.osdu.register.provider.interfaces.subscriber;
+
+import org.opengroup.osdu.core.common.model.notification.Topic;
+
+import java.util.List;
+
+public interface ITopicsRepository {
+    List<Topic> listMessages();
+}