Storage merge requestshttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests2024-01-09T10:29:38Zhttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/816ibm-lib version upgrade2024-01-09T10:29:38ZAshwani Pandeyibm-lib version upgradecore-lib-ibm version upgrade to 0.25.1core-lib-ibm version upgrade to 0.25.1M22 - Release 0.25Ashwani PandeyAshwani Pandeyhttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/186hot fix to generate artifact2021-04-15T21:13:19ZSanjeev-SLBhot fix to generate artifact# Merge request template# Merge request templatehttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/598Handling data inconsistency properly (GONRG-6319)2023-02-06T16:09:54ZKanstantsin Dubrouski [EPAM / GCP]Handling data inconsistency properly (GONRG-6319)Handling data inconsistency properlyHandling data inconsistency properlyM16 - Release 0.19Riabokon Stanislav(EPAM)[GCP]Riabokon Stanislav(EPAM)[GCP]https://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/569GONRG-6045: Remove NEG annotation in service2022-12-06T11:35:06ZVolodymyr Pienskoi [EPAM / GCP]GONRG-6045: Remove NEG annotation in serviceServices created in GKE clusters 1.17.6-gke.7 and up with VPC-native traffic routing enabled are annotated automatically with `cloud.google.com/neg: '{"ingress": true}'`. This means that this annotation is not required explicitly and can...Services created in GKE clusters 1.17.6-gke.7 and up with VPC-native traffic routing enabled are annotated automatically with `cloud.google.com/neg: '{"ingress": true}'`. This means that this annotation is not required explicitly and can be removed.
More details in [GKE Load Balancing documentation](https://cloud.google.com/kubernetes-engine/docs/concepts/ingress#container-native_load_balancing).Volodymyr Pienskoi [EPAM / GCP]Volodymyr Pienskoi [EPAM / GCP]https://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/443GONRG-5182-external-postgresql-anthos-df2022-08-05T08:54:32ZSiarhei Symanovich (EPAM)GONRG-5182-external-postgresql-anthos-dfadded partitionIDadded partitionIDSiarhei Symanovich (EPAM)Siarhei Symanovich (EPAM)https://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/10Generate required test data in the integration tests2020-05-20T17:37:34ZWyatt NielsenGenerate required test data in the integration testsUpdated integration test setup to generate data for tests instead of depending on data already in environment. Update cloudStorageImpl and
RecordsMetadataRepositoryImpl to handle user verification in the same way as other osdu implement...Updated integration test setup to generate data for tests instead of depending on data already in environment. Update cloudStorageImpl and
RecordsMetadataRepositoryImpl to handle user verification in the same way as other osdu implementationshttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/673Full Upgrade of First Party Library Dependencies for Release 0.202023-05-22T15:18:34ZDavid Diederichd.diederich@opengroup.orgFull Upgrade of First Party Library Dependencies for Release 0.20This generated MR upgrades the first party libraries (other OSDU libraries) to utilize the latest release.
The intent is to try to fully upgrade all dependent libraries to see if the latest code will work.
It is expected that these will ...This generated MR upgrades the first party libraries (other OSDU libraries) to utilize the latest release.
The intent is to try to fully upgrade all dependent libraries to see if the latest code will work.
It is expected that these will often fail, since the upgrades were previously rejected for failing pipelines and have not been directly addressed yet.
This 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.
This MR may co-exist with a separate, smaller upgrade MR.
If both pass, this one should be used instead.
### Dependency Information Before the Upgrade
```
Branch: master
SHA: f94322cf62a0d949e6a640b209dd2a2fa1ea5ead
Maven: 0.21.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------------------------------------------- | --------------- | ---------------------- |
| core-lib-azure | 0.20.0-rc8 | |
| core-lib-gc | 0.21.0-rc1 | |
| os-core-lib-aws | 0.21.0-SNAPSHOT | 0.19.0-rc3 |
| obm | 0.20.0-rc2 | |
| oqm | 0.19.0 | |
| os-core-common | 0.20.0-rc3 | 0.13.0, 0.18.0-rc3 |
| os-core-lib-ibm | 0.17.0-rc4 | 0.17.0-rc4 |
| osm | 0.21.0-rc1 | |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.14.0 | 2.8.1, 2.13.2.2 |
| (3rd Party) org.springframework.spring-webmvc | 5.3.26, 5.3.22 | 5.3.12, 5.3.24, 5.3.22 |
| (3rd Party) org.yaml.snakeyaml | 2.0 | 1.27, 1.30 |
### Dependency Information After the Upgrade
```
Branch: dependency-upgrade
SHA: 043bdc96420db671b2ff939b1614d95cd57f3266
Maven: 0.21.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------------------------------------------- | ---------- | --------------- |
| core-lib-azure | 0.20.0 | |
| core-lib-gc | 0.21.0-rc3 | |
| os-core-lib-aws | 0.20.0 | 0.20.0 |
| obm | 0.20.0 | |
| oqm | 0.20.0 | |
| os-core-common | 0.20.1 | 0.20.1 |
| os-core-lib-ibm | 0.20.0 | 0.20.0 |
| osm | 0.21.0-rc2 | |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.14.0 | 2.8.1, 2.13.2.2 |
| (3rd Party) org.yaml.snakeyaml | 2.0 | 1.30, 2.0 |M18 - Release 0.21Okoun-Ola Fabien HouetoBrindaban DasYauhen Shaliou [EPAM/GCP]Srinivasan NarayananOkoun-Ola Fabien Houetohttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/467Fix surefire2022-07-29T17:03:05ZRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comFix surefire# Merge request template# Merge request templatehttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/172Fix pod restarts on health check failues2021-08-30T21:34:36ZAlok JoshiFix pod restarts on health check failuesAfter pulling in this MR https://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/149, we observed (in our internal ADO) that
- health check endpoint logs were missing from application insights and Log Analytics
- po...After pulling in this MR https://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/149, we observed (in our internal ADO) that
- health check endpoint logs were missing from application insights and Log Analytics
- pods were not getting restarted when health checks were down
- [line51](https://community.opengroup.org/osdu/platform/system/storage/-/blob/master/devops/azure/chart/templates/deployment.yaml) line 51 says have to upgrade to Spring Boot 2.3 but I believe we are on 2.1.18.RELEASE
- Falling back to actuator health check by `spring-boot-starter-actuator`
@krveduruAlok JoshiAlok Joshihttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/568fix IT with retry2023-08-25T22:28:44ZNikhil Singh[MicroSoft]fix IT with retry# Merge request template# Merge request templateNikhil Singh[MicroSoft]Nikhil Singh[MicroSoft]https://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/719Fix instance name2023-06-29T15:34:33ZAleh Shubko [EPAM]Fix instance nameM19 - Release 0.22Madalyn MarabellaMadalyn Marabellahttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/295Fixing ACL for Integration tests2022-07-12T15:38:43ZRonak SakhujaFixing ACL for Integration tests# Merge request template# Merge request templatehttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/466Fixed usage of AzureServicePrincipal2022-08-03T13:27:04ZDmitrii Novikov (EPAM)Fixed usage of AzureServicePrincipal## Type of change
- [x] Bug Fix
- [ ] 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
- [x] Azure
- [ ] GCP
- [ ] IB...## Type of change
- [x] Bug Fix
- [ ] 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
- [x] Azure
- [ ] GCP
- [ ] IBM
## Any other useful information
Azure service principal usage in tests replaced with class from core-lib-azureDmitrii Novikov (EPAM)Dmitrii Novikov (EPAM)https://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/471Fixed azure tests2022-08-05T15:06:54ZDmitrii Novikov (EPAM)Fixed azure tests## Type of change
- [x] Bug Fix
- [ ] 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
- [x] Azure
- [ ] GCP
- [ ] IB...## Type of change
- [x] Bug Fix
- [ ] 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
- [x] Azure
- [ ] GCP
- [ ] IBM
## Does this introduce a breaking change?
- [NO]
Fixed azure testsM13 - Release 0.16Dmitrii Novikov (EPAM)Dmitrii Novikov (EPAM)https://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/821Fix/collab header22024-01-12T16:11:28ZMark ChanceFix/collab header2[**AWS implementation support for Collboration Header**](/osdu/platform/system/storage/-/commit/0ac8ba115cb5ec8998abb2e90b64ce510e9ae999)[**AWS implementation support for Collboration Header**](/osdu/platform/system/storage/-/commit/0ac8ba115cb5ec8998abb2e90b64ce510e9ae999)https://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/488fix api test2023-02-04T05:34:22ZNikhil Singh[MicroSoft]fix api test# Merge request template# Merge request templateNikhil Singh[MicroSoft]Nikhil Singh[MicroSoft]https://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/652Filter metadata records by partition id2023-03-16T20:45:06ZMorris EstepaFilter metadata records by partition id## Type of change
- [X] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
https://community.opengroup.org/osdu/platform/system/storage/-/issues/167
## Does this introduce a change in ...## Type of change
- [X] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
https://community.opengroup.org/osdu/platform/system/storage/-/issues/167
## 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?
metadata records from other data partition ids show up when querying records for a given partition id
## What is the new/expected behavior?
only metadata records from the target partition id shows up in the query results
## Have you added/updated Unit Tests and Integration Tests?
Yes
## Any other useful informationM16 - Release 0.19Morris EstepaMorris Estepahttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/136Fail fast before fetching blob2021-02-09T22:33:13ZHema Vishnu Pola [Microsoft]Fail fast before fetching blob## 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] - Instead of waiting to fetch blob and then failin...## 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] - Instead of waiting to fetch blob and then failing in ACL, made to fail fast and fetch the blob post that. Please do validate if it does make sense and doesn't disturb any of the flow.
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [ ] Azure
- [ ] GCP
- [ ] IBM
## Does this introduce a breaking change?
- [NO]
## What is the current behavior?
After fetching the blob, then ACL checks are done.
## What is the new/expected behavior?
Reversing the order to fetch blob only when ACL checks succeed. This would allow to fail fast before loading the whole blob.
## Have you added/updated Unit Tests and Integration Tests?
## Any other useful informationhttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/37Enforce that user must have ACL groups access of the Record for purge, create...2020-07-16T14:17:15ZJohnny Guojguo26@slb.comEnforce that user must have ACL groups access of the Record for purge, create and update operations.• What is the change?
This change is to make sure that if a user wants to purge/update/create a record, the user must have access to record ACL groups, which means be a member of any ACL group of the record.
• What does it impact?
If a ...• What is the change?
This change is to make sure that if a user wants to purge/update/create a record, the user must have access to record ACL groups, which means be a member of any ACL group of the record.
• What does it impact?
If a user does not belong to any ACL group of the record, he/she cannot update/create/purge it after the PR is merged.
• How do I reproduce or test the change?
Here I add and update unit tests and integration tests, you can also manually test the deployment.ethiraj krishnamanaiduBrandt BealNeelesh ThakurDaniel SchollAlok JoshiRostislav Vatolinvatolinrp@gmail.comHong Yanethiraj krishnamanaiduhttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/41Enforce record owner access fix line separator2020-07-16T14:54:40ZJohnny Guojguo26@slb.comEnforce record owner access fix line separator• What is the change?
This change is to make sure that if a user wants to purge/update/create a record, the user must have access to record ACL groups, which means be a member of any ACL group of the record.
• What does it impact?
If a ...• What is the change?
This change is to make sure that if a user wants to purge/update/create a record, the user must have access to record ACL groups, which means be a member of any ACL group of the record.
• What does it impact?
If a user does not belong to any ACL group of the record, he/she cannot update/create/purge it after the PR is merged.
• How do I reproduce or test the change?
Here I add and update unit tests and integration tests, you can also manually test the deployment.