Schema merge requestshttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests2023-08-18T22:00:25Zhttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/58Slb multipartition for azure2023-08-18T22:00:25ZAbhishek Kumar (SLB)Slb multipartition for azureContributing the changes pertaining to multi-partition support of schema-service.
Now, schema-service depends on partition-service to interact with different partition depending upon the data-partition-id passed in the header.Contributing the changes pertaining to multi-partition support of schema-service.
Now, schema-service depends on partition-service to interact with different partition depending upon the data-partition-id passed in the header.M3 - Release 0.5ethiraj krishnamanaiduKishore Battulaethiraj krishnamanaiduhttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/69Audit Logger Implementation (GONRG-1547)2023-08-18T21:58:39ZArtem Dobrynin (EPAM)Audit Logger Implementation (GONRG-1547)# Description:
1.Added audit log events according to this issue: https://community.opengroup.org/osdu/platform/deployment-and-operations/audit-and-metrics/-/issues/13
2.Minor fix core libs conflict for gcp provider:
core-lib-gcp(0.1.15...# Description:
1.Added audit log events according to this issue: https://community.opengroup.org/osdu/platform/deployment-and-operations/audit-and-metrics/-/issues/13
2.Minor fix core libs conflict for gcp provider:
core-lib-gcp(0.1.15) uses methods that not present in core-common that leads to
(NoSuchMethodError: org.opengroup.osdu.core.common.http.HttpResponse.getAsJsonObject())
* Update core-lib-gcp from `0.1.15` to `0.3.25`
* Fix related methods & unit tests
# How to test:
Bussines cases (Schema Service API).
# Changes include:
* [ ] Refactor (a non-breaking change that improves code maintainability).
* [x] Bugfix (a non-breaking change that solves an issue).
* [x] New feature (a non-breaking change that adds functionality).
* [ ] Breaking change (a change that is not backward-compatible and/or changes current functionality).
# Changes in:
* [X] Core
* [x] GCP
* [ ] Azure
* [ ] AWS
* [ ] IBM
# Dev Checklist:
* [x] Added Unit Tests, wherever applicable.
* [ ] Updated the Readme, if applicable.
* [x] Existing Tests pass
* [x] Verified functionality locally
* [x] Self Reviewed my code for formatting and complex business logic.M3 - Release 0.5Rostislav Dublin (EPAM)Rostislav Dublin (EPAM)https://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/103Schema Notification2023-08-18T21:58:08ZAbhishek Kumar (SLB)Schema NotificationWith schema notification changes there will be a notification triggered on the event-grid topic.
There is a new contract introduced in the core module `IMessageBus` with the below signature:
```
public interface IMessageBus {
void publi...With schema notification changes there will be a notification triggered on the event-grid topic.
There is a new contract introduced in the core module `IMessageBus` with the below signature:
```
public interface IMessageBus {
void publishMessage(String schemaId, String eventType);
}
```
This is a breaking change for the rest of the vendors but to avoid any run time issues below stub is added which is expected to implemented by each vendor.
```
@Component
public class MessageBusImpl implements IMessageBus{
@Inject
private JaxRsDpsLog logger;
@Override
public void publishMessage(String schemaId, String eventType) {
// TODO Auto-generated method stub
logger.warning("publish message not implemented ye");
}
}
```
## Runtime variables:
By default, notification feature is turned off using the below parameter:
```
azure.eventGrid.enabled=${event_grid_enabled}
```
Value of this parameter can be found at: `\schema-service\devops\azure\chart\templates\deployment.yaml`
```
- name: event_grid_enabled
value: "false"
```M6 - Release 0.9Paresh BehedeParesh Behede