Storage merge requestshttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests2022-09-16T07:47:20Zhttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/383Opa integration to replicate existing data authz in Storage Service2022-09-16T07:47:20ZKelly ZhouOpa integration to replicate existing data authz in Storage ServicePlease refer to issue: https://community.opengroup.org/osdu/platform/security-and-compliance/policy/-/issues/34Please refer to issue: https://community.opengroup.org/osdu/platform/security-and-compliance/policy/-/issues/34M11 - Release 0.14https://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/384Trusted additional attributes in delete event2022-03-17T10:00:42ZVaishali MangwaniTrusted additional attributes in delete event# Merge request template# Merge request templatehttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/385Draft: Trusted additional attributes in delete event2022-03-17T13:48:10ZVaishali MangwaniDraft: Trusted additional attributes in delete event# Merge request template# Merge request templatehttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/386Remove the definition of os-core-common version in storage-aws2022-03-21T17:07:37ZYifei XuRemove the definition of os-core-common version in storage-aws## Type of change
- [x] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a change in the core logic?
- [NO]
## Does this introduce a change in the cloud provi...## Type of change
- [x] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a change in the core logic?
- [NO]
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [x] AWS
- [ ] Azure
- [ ] GCP
- [ ] IBM
## Does this introduce a breaking change?
- [NO]
## What is the current behavior?
## What is the new/expected behavior?
## Have you added/updated Unit Tests and Integration Tests?
## Any other useful informationM11 - Release 0.14JoeYifei XuOkoun-Ola Fabien HouetoJoehttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/387update DatesConversion for the nested properties (increase os-core-common ver...2022-09-16T07:41:25ZYauheni Lesnikauupdate DatesConversion for the nested properties (increase os-core-common version)Issue: https://community.opengroup.org/osdu/platform/system/storage/-/issues/115Issue: https://community.opengroup.org/osdu/platform/system/storage/-/issues/115M11 - Release 0.14Yauheni LesnikauYauheni Lesnikauhttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/388Updating storage service to use RedisAzureCache2022-03-28T17:09:50ZShiv SinghUpdating storage service to use RedisAzureCache# Merge request template# Merge request templateShiv SinghShiv Singhhttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/389Added user email attribute to OqmMessage (EPAM - GONRG-4620)2023-08-18T22:21:41ZDmitrii Novikov (EPAM)Added user email attribute to OqmMessage (EPAM - GONRG-4620)## Type of change
- [ ] Bug Fix
- [x] Feature
https://jiraeu.epam.com/browse/GONRG-4620
## Does this introduce a change in the core logic?
- [NO]
## Does this introduce a change in the cloud provider implementation, if so which cloud...## Type of change
- [ ] Bug Fix
- [x] Feature
https://jiraeu.epam.com/browse/GONRG-4620
## Does this introduce a change in the core logic?
- [NO]
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [ ] Azure
- [x] GCP
- [ ] IBM
## Does this introduce a breaking change?
- [NO]
## What is the current behavior?
Added user email attibute to OqmMessage for AuditLogger in IndexerService.M11 - Release 0.14Riabokon Stanislav(EPAM)[GCP]Riabokon Stanislav(EPAM)[GCP]https://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/390Updated storage service to use RedisAzureCache2023-08-18T22:21:39ZShiv SinghUpdated storage service to use RedisAzureCache# Merge request template# Merge request templateM11 - Release 0.14Shiv SinghShiv Singhhttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/391Update helms for anthos on-prem usage [GONRG-4557]2023-08-18T22:21:38ZMikhail Piatliou (EPAM)Update helms for anthos on-prem usage [GONRG-4557]# Merge request template# Merge request templateM12 - Release 0.15Mikhail Piatliou (EPAM)Mikhail Piatliou (EPAM)https://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/392Removed StorageConfigProperties. Fixed typos in README files (GONRG-4534)2022-03-29T12:57:31ZRiabokon Stanislav(EPAM)[GCP]Removed StorageConfigProperties. Fixed typos in README files (GONRG-4534)## Type of change
- [x] Bug Fix
- [ ] Feature
Removed StorageConfigProperties. Fixed typos in README files.
## Does this introduce a change in the core logic?
- [NO]
## Does this introduce a change in the cloud provider implementatio...## Type of change
- [x] Bug Fix
- [ ] Feature
Removed StorageConfigProperties. Fixed typos in README files.
## Does this introduce a change in the core logic?
- [NO]
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [ ] Azure
- [x] GCP
- [ ] IBMM11 - Release 0.14Riabokon Stanislav(EPAM)[GCP]Riabokon Stanislav(EPAM)[GCP]https://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/393Upgrade First Party Library Dependencies for Release 0.142022-04-05T10:39:13ZDavid Diederichd.diederich@opengroup.orgUpgrade First Party Library Dependencies for Release 0.14This automated MR upgrades the first party libraries (other OSDU libraries) to utilize the latest release.
The intent is to keep the OSDU projects utilizing the latest available code to ensure widespread usage and stability.
However, any...This automated MR upgrades the first party libraries (other OSDU libraries) to utilize the latest release.
The intent is to keep the OSDU projects utilizing the latest available code to ensure widespread usage and stability.
However, any library that is older than the previous release will be left as-is, since the upgrade is likely to be more complicated.
Furthermore, the upgrade should only be merged in the CI pipeline reports success.
If this MR has failed, we can spend a little time investigating to see if a trivial upgrade could achieve compatiblity to the new library.
But significant upgrade efforts should not occur on this MR, as part of the release tagging process.
Instead, significant work should be scheduled for a subsequent milestone.
### Dependency Information Before the Upgrade
```
Branch: master
SHA: 78528a84830e9bdec9fac22e14df1884f9dba976
Maven: 0.14.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | provider/storage-aws/src/main/ComplianceTrigger/ComplianceTriggerFunction/ComplianceTriggerFunction/ | testing/ |
| --------------------------------------------------- | ---------------------- | ---------------------------------------------------------------------------------------------------- | ------------- |
| core-lib-azure | 0.14.0-rc3 | | |
| core-lib-gcp | 0.14.0-rc2, 0.13.0 | | |
| os-core-lib-aws | 0.13.0, 0.3.8 | 0.10.0 | 0.10.0, 0.3.7 |
| obm | 0.13.1-SNAPSHOT | | |
| oqm | 0.13.0-SNAPSHOT | | |
| os-core-common | 0.14.0-rc6, 0.14.0-rc8 | 0.13.0 | 0.13.0 |
| os-core-lib-ibm | 0.13.0 | | 0.13.0 |
| osm | 0.13.0-SNAPSHOT | | |
| (3rd Party) net.minidev.json-smart | 2.4.7 | | 2.3 |
| (3rd Party) org.apache.logging.log4j.log4j-api | 2.17.1 | 2.13.3 | 2.17.1 |
| (3rd Party) org.apache.logging.log4j.log4j-to-slf4j | 2.17.1 | 2.13.3 | 2.17.1 |
### Dependency Information After the Upgrade
```
Branch: dependency-upgrade
SHA: 84cea0aed4d76c3fc55e7155d72c72410b1f7171
Maven: 0.14.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | provider/storage-aws/src/main/ComplianceTrigger/ComplianceTriggerFunction/ComplianceTriggerFunction/ | testing/ |
| --------------------------------------------------- | ------------- | ---------------------------------------------------------------------------------------------------- | ------------- |
| core-lib-azure | 0.14.0 | | |
| core-lib-gcp | 0.14.0 | | |
| os-core-lib-aws | 0.14.0, 0.3.8 | 0.10.0 | 0.10.0, 0.3.7 |
| obm | 0.14.0 | | |
| oqm | 0.14.0 | | |
| os-core-common | 0.14.0 | 0.14.0 | 0.14.0 |
| os-core-lib-ibm | 0.14.0 | | 0.14.0 |
| osm | 0.14.0 | | |
| (3rd Party) net.minidev.json-smart | 2.4.7 | | 2.3 |
| (3rd Party) org.apache.logging.log4j.log4j-api | 2.17.1 | 2.13.3 | 2.17.1 |
| (3rd Party) org.apache.logging.log4j.log4j-to-slf4j | 2.17.1 | 2.13.3 | 2.17.1 |M11 - Release 0.14https://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/394Upgrade First Party Library Dependencies for Release 0.14 (Except Azure)2022-04-05T10:39:19ZDavid Diederichd.diederich@opengroup.orgUpgrade First Party Library Dependencies for Release 0.14 (Except Azure)This is related to !393, except it holds back the Azure dependency -- based on the result that the Azure tests failed in !393.
### Dependency Information After the Upgrade
```
Branch: dependency-upgrade-except-azure
SHA: 9b114713afc...This is related to !393, except it holds back the Azure dependency -- based on the result that the Azure tests failed in !393.
### Dependency Information After the Upgrade
```
Branch: dependency-upgrade-except-azure
SHA: 9b114713afc424bd95d6f655f1834bffcb0cf9f1
Maven: 0.15.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | provider/storage-aws/src/main/ComplianceTrigger/ComplianceTriggerFunction/ComplianceTriggerFunction/ | testing/ |
| --------------------------------------------------- | ------------- | ---------------------------------------------------------------------------------------------------- | ------------- |
| core-lib-azure | 0.14.0-rc5 | | |
| core-lib-gcp | 0.14.0 | | |
| os-core-lib-aws | 0.14.0, 0.3.8 | 0.10.0 | 0.10.0, 0.3.7 |
| obm | 0.14.0 | | |
| oqm | 0.14.0 | | |
| os-core-common | 0.14.0 | 0.14.0 | 0.14.0 |
| os-core-lib-ibm | 0.14.0 | | 0.14.0 |
| osm | 0.14.0 | | |
| (3rd Party) net.minidev.json-smart | 2.4.7 | | 2.3 |
| (3rd Party) org.apache.logging.log4j.log4j-api | 2.17.1 | 2.13.3 | 2.17.1 |
| (3rd Party) org.apache.logging.log4j.log4j-to-slf4j | 2.17.1 | 2.13.3 | 2.17.1 |David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/395modified log for legal compliance async processing2023-08-18T22:21:36ZYauheni Lesnikaumodified log for legal compliance async processingMake logging more relevant to the performing operation
Issue: https://community.opengroup.org/osdu/platform/system/storage/-/issues/118Make logging more relevant to the performing operation
Issue: https://community.opengroup.org/osdu/platform/system/storage/-/issues/118M12 - Release 0.15Yauheni LesnikauYauheni Lesnikauhttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/396Updating NOTICE2022-04-04T18:49:58ZDavid Diederichd.diederich@opengroup.orgUpdating NOTICEM11 - Release 0.14David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/397Cherry-pick "Limit exception remove" into release/0.142022-04-04T20:41:27ZDavid Diederichd.diederich@opengroup.orgCherry-pick "Limit exception remove" into release/0.14Original MR: !377Original MR: !377M11 - Release 0.14David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/398Cherry-pick - branch 'akprasad/remove-limit' into release 0.142022-04-04T20:40:22ZDebasis ChatterjeeCherry-pick - branch 'akprasad/remove-limit' into release 0.14!377!377https://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/399Updated storage service to use RedisAzureCache2023-02-04T05:34:22ZShiv SinghUpdated storage service to use RedisAzureCache# Merge request template# Merge request templateShiv SinghShiv Singhhttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/400Disable schema endpoints via flag2023-08-18T22:21:34ZAlok JoshiDisable schema endpoints via flagDisable schema endpoints with feature flagDisable schema endpoints with feature flagM12 - Release 0.15Alok JoshiAlok Joshihttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/401gcp-untie-messaging-from-http(GONRG-4640)2022-04-19T14:59:57ZRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comgcp-untie-messaging-from-http(GONRG-4640)## Type of change
- [ ] Bug Fix
- [x] Feature
## Does this introduce a change in the core logic?
- [NO]
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [ ] Azure
- [x] GCP
- [ ] IB...## Type of change
- [ ] Bug Fix
- [x] Feature
## Does this introduce a change in the core logic?
- [NO]
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [ ] Azure
- [x] GCP
- [ ] IBM
## Does this introduce a breaking change?
- [YES]
## What is the current behavior?
Storage after migration to OQM service is not able to process `legal_changed` events due to request scope boundaries in common code, because OQM is designed to use only pull subscribers.
## What is the new/expected behavior?
Storage service context was split into two separate contexts, one for serving HTTP requests via API that is still bound to request scope,
and one for message event processing which contains overridden bean definitions, not limited with request scope.
## Have you added/updated Unit Tests and Integration Tests?
YesM12 - Release 0.15Riabokon Stanislav(EPAM)[GCP]Riabokon Stanislav(EPAM)[GCP]https://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/402Update devops/azure/chart/templates/deployment.yaml2022-04-19T04:31:40ZMANISH KUMARUpdate devops/azure/chart/templates/deployment.yaml## Type of change
- [X] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a change in the core logic?
- [YES/NO]
## Does this introduce a change in the cloud p...## Type of change
- [X] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a change in the core logic?
- [YES/NO]
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [X] Azure
- [ ] GCP
- [ ] IBM
## Does this introduce a breaking change?
- [NO]
## What is the current behavior?
GC doesn't trigger for high memory when load is high
## What is the new/expected behavior?
GC triggers and application doesn't crash on a high load
## Have you added/updated Unit Tests and Integration Tests?
NA
## Any other useful information
Updating GC to G1M12 - Release 0.15MANISH KUMARMANISH KUMAR