Policy as a feature

Type of change

• Bug Fix
• Feature

Current Epic: osdu/platform&29

OPA\Policy Integration (Configured mostly through properties, Storage, Search).

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
• Google Cloud
• IBM

Does this introduce a breaking change?

• [YES]

Currently, the Policy enabled flag which decides whether or not to use Policy service is coming from the application properties file, this MR is made to use the function flag to use Policy as a feature. So the flag can be fetched from partition property, environment variable featureFlag.policy.enabled.

docs/docs/PolicyService-Integration.md

@@ -10,11 +10,10 @@ Search service combines the user query with the Elasticsearch Query DSL translat
 
 - Add and provide values for following runtime configuration in `application.properties`:
 ```
-  service.policy.enabled=true
+  featureFlag.policy.enabled=true
   service.policy.id=${policy_id}
   service.policy.endpoint=${policy_service_endpoint}
-  policy.cache.timeout=<timeout_in_minutes>
-  PARTITION_API=${partition_service_endpoint}
+  service.policy.cache.timeout=<timeout_in_minutes>
 ```
 The policy id can be an instance based id (ie, osdu.instance.search) or partition based id (ie, osdu.partiton["%s"].search).