PoC of change-based configuration using MerkleTree

The goal of this MR is to check if storing application configuration
fetched from CBS in Merkle Tree would be a good approach.

CoS:
- it should be possible to refetch configuration at some intervals
- any new update should trigger changes in affected modules, ie. change
  of dmaap topics should trigger changes in dmaap client but not in aai
  client

In order to satisfy this requirement a MerkleTree-based solution was
proposed. The structure keeps track of hashes of each node and its
subnodes. In case of a change in one branch the hash of other sibling
branch will not change.

Change-Id: I034be0f67d8522025a49a6ac8311b7efb8452765
Issue-ID: DCAEGEN2-884
Signed-off-by: Piotr Jaszczyk <piotr.jaszczyk@nokia.com>

1 files changed, 14 insertions, 5 deletions

diff --git a/rest-services/cbs-client/pom.xml b/rest-services/cbs-client/pom.xml
index 2580762d..a3424b63 100644
--- a/rest-services/cbs-client/pom.xml
+++ b/rest-services/cbs-client/pom.xml
@@ -37,6 +37,11 @@
       <artifactId>gson</artifactId>
     </dependency>
     <dependency>
+      <groupId>io.vavr</groupId>
+      <artifactId>vavr
+      </artifactId>
+    </dependency>
+    <dependency>
       <groupId>io.projectreactor</groupId>
       <artifactId>reactor-core</artifactId>
     </dependency>
@@ -62,11 +67,15 @@
       <artifactId>mockito-core</artifactId>
       <scope>test</scope>
     </dependency>
-    <dependency>
-      <groupId>org.junit.jupiter</groupId>
-      <artifactId>junit-jupiter-engine</artifactId>
-      <scope>test</scope>
-    </dependency>
+      <dependency>
+          <groupId>org.junit.jupiter</groupId>
+          <artifactId>junit-jupiter-engine</artifactId>
+          <scope>test</scope>
+      </dependency>
+      <dependency>
+          <groupId>org.assertj</groupId>
+          <artifactId>assertj-core</artifactId>
+      </dependency>
     <dependency>
       <groupId>io.projectreactor</groupId>
       <artifactId>reactor-test</artifactId>