FINERACT-1571: Allow Liquibase data migration for write instances only

fineract-provider/src/test/resources/application-test.properties

@@ -33,6 +33,10 @@ fineract.tenant.identifier=default
 fineract.tenant.name=fineract_default
 fineract.tenant.description=Default Demo Tenant
 
+fineract.mode.read-enabled=true
+fineract.mode.write-enabled=true
+fineract.mode.batch-enabled=true
+
 management.health.jms.enabled=false
 
 # FINERACT 1296

fineract-provider/src/test/resources/features/infrastructure/infrastructure.core.feature

@@ -6,8 +6,26 @@ Feature: Core Infrastructure
     When The database migration process is executed
     Then The database migration did not do anything
 
+  @infrastructure
+  Scenario: Verify that schema migration is not executed when the Fineract instance is a read instance
+    Given Set every Fineract instance type to false
+    Given Fineract instance is a read instance
+    Given Liquibase is enabled with a default tenant
+    When The database migration process is executed
+    Then The database migration did not do anything, because it is not a write instance
+
+  @infrastructure
+  Scenario: Verify that schema migration is not executed when the Fineract instance is a batch instance
+    Given Set every Fineract instance type to false
+    Given Fineract instance is a batch instance
+    Given Liquibase is enabled with a default tenant
+    When The database migration process is executed
+    Then The database migration did not do anything, because it is not a write instance
+
   @infrastructure
   Scenario: Verify that schema migration works from scratch
+    Given Set every Fineract instance type to false
+    Given Fineract instance is a write instance
     Given Liquibase is enabled with a default tenant
     Given Liquibase runs the very first time for the tenant store
     Given Liquibase runs the very first time for the default tenant