OS Core Common - Spring 5 merge requestshttps://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/merge_requests2023-08-18T23:34:56Zhttps://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/merge_requests/227AWS sync dev to master2023-08-18T23:34:56ZLong ChengAWS sync dev to masterM20 - Release 0.23Long ChengLong Chenghttps://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/merge_requests/106Hotfix context for CloudVersionInfoBuilder2021-07-27T15:28:47ZDmitrii Novikov (EPAM)Hotfix context for CloudVersionInfoBuilderM7 - Release 0.10Rostislav Dublin (EPAM)Rostislav Dublin (EPAM)https://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/merge_requests/260merge with no change2024-03-19T17:14:51ZYunhua Koglinmerge with no changeM23 - Release 0.26Yunhua KoglinYunhua Koglinhttps://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/merge_requests/240Solxget/vulnerabilities2023-11-09T18:57:45ZSolomon AyalewSolxget/vulnerabilitiesUpgrade Spring boot and other dependancy versions to elimnate vulnerabilitiesUpgrade Spring boot and other dependancy versions to elimnate vulnerabilitiesM22 - Release 0.25https://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/merge_requests/205Cherry-pick 'upgrading dependencies' into release/0.202023-04-07T14:35:00ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'upgrading dependencies' into release/0.20**Original MR**: !204
### This MR is a Cherry Pick into a Release Branch.
After the release branch is first created, any subsequent changes use this process to update the release (often resulting in a new patch tag) without incorporati...**Original MR**: !204
### This MR is a Cherry Pick into a Release Branch.
After the release branch is first created, any subsequent changes use this process to update the release (often resulting in a new patch tag) without incorporating all changes in the default branch.
These MRs must be approved by the PMC before they are merged, since they alter the scope of the release.
To see more details about the change itself, look at the Original MR listed above.
#### Skipped Pipeline
Normally, pipelines are not executed on the cherry pick branch/MR prior to merging.
This optimization is accepted because the code was tested when it merged into the default branch, and will be tested again in the release branch prior to tagging.
However, if anybody feels that the MR requires further scrutiny -- whether because it had conflicts in the cherry-picking, it interfaces with some drastically altered logic between the branches, or any other reason -- we can run the pipeline here prior to merging.
#### If There's Reason to Run a Pipeline
If you want to see a pipeline result before this merges, first add a comment explaining why you'd like to see the pipeline results so the PMC and others know your thinking.
Then, mark the MR as a Draft MR (using the vertical ellipsis above, choose 'Mark as Draft').
This prevents the MR from being approved & merged accidentally by a busy release coordinator who didn't see your comment.
Finally, if you are a maintainer on the project, launch a pipeline on this branch.
Since this branch is a protected branch and the MR has ~no-detached-pipeline set, all integration tests will run and there's no need for any `trusted-*` branches.
[Launch a Pipeline for this Branch](https://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/pipelines/new?ref=cherry-pick-for-204)M17 - Release 0.20David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/merge_requests/204upgrading dependencies2023-04-07T03:22:43ZAbhay Joshiupgrading dependenciesM17 - Release 0.20Okoun-Ola Fabien HouetoAbhay JoshiOkoun-Ola Fabien Houetohttps://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/merge_requests/175[CRS normalization] Ingested manifest with 2D CRS Persistable reference canno...2022-09-28T07:01:57ZRiabokon Stanislav(EPAM)[GCP][CRS normalization] Ingested manifest with 2D CRS Persistable reference cannot be found by Search (GONRG-5581)Issue: https://community.opengroup.org/osdu/platform/system/indexer-service/-/issues/61
There is a bug in the core common lib util class: https://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/blob/master/src/mai...Issue: https://community.opengroup.org/osdu/platform/system/indexer-service/-/issues/61
There is a bug in the core common lib util class: https://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/blob/master/src/main/java/org/opengroup/osdu/core/common/util/JsonUtils.java#L84
Storage service uses this class when records are requested via `query` endpoint:
~~~
curl --location --request POST 'https://preship.gcp.gnrg-osdu.projects.epam.com/api/storage/v2/query/records:batch' \
--header 'Data-Partition-ID: odesprod' \
--header 'frame-of-reference: units=SI;crs=wgs84;elevation=msl;azimuth=true north;dates=utc;' \
--header 'Authorization: Bearer ' \
--header 'Content-Type: application/json' \
--data-raw '{
"records":[
"odesprod:work-product-component--SeismicBinGrid:10May2Dpoly"
]
}'
~~~
The same endpoint is used by the Indexer service to perform indexing on converted records.
When there is a conversion property in array format like `VerticalMeasurements[].VerticalMeasurement` present in the record `meta` block but not present in the data section, this method throws `NullPointerException`. Which makes Storage to respond a `500` error and breaks the indexing of that record.
![npe](/uploads/c9427e897975eea976723cbb6d1fa9bb/npe.png)M14 - Release 0.17Riabokon Stanislav(EPAM)[GCP]Riabokon Stanislav(EPAM)[GCP]https://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/merge_requests/112Hotfix pom version2023-08-18T13:07:31ZDmitrii Novikov (EPAM)Hotfix pom versionM8 - Release 0.11Rostislav Dublin (EPAM)Rostislav Dublin (EPAM)https://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/merge_requests/110Connected outer services for version info endpoint (GONRG-2681)2022-09-16T08:52:53ZDmitrii Novikov (EPAM)Connected outer services for version info endpoint (GONRG-2681)## Type of change
- [ ] Bug Fix
- [x] Feature
osdu/platform/system/lib/core/os-core-common#47
## Does this introduce a change in the core logic?
- [YES]
## Does this introduce a change in the cloud provider implementation, if so whic...## Type of change
- [ ] Bug Fix
- [x] Feature
osdu/platform/system/lib/core/os-core-common#47
## Does this introduce a change in the core logic?
- [YES]
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [x] AWS
- [x] Azure
- [x] GCP
- [x] IBM
## Does this introduce a breaking change?
- [YES]
## What is the current behavior?
Provides connected outer services infoM8 - Release 0.11Rostislav Dublin (EPAM)Rostislav Dublin (EPAM)https://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/merge_requests/107Added new version info endpoint (GONRG-2681)2022-09-16T08:52:05ZDmitrii Novikov (EPAM)Added new version info endpoint (GONRG-2681)reopened MR related to https://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/merge_requests/103
## Type of change
- [ ] Bug Fix
- [x] Feature
osdu/platform/system/lib/core/os-core-common#47
## Does this introd...reopened MR related to https://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/merge_requests/103
## Type of change
- [ ] Bug Fix
- [x] Feature
osdu/platform/system/lib/core/os-core-common#47
## Does this introduce a change in the core logic?
- [YES]
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [x] AWS
- [x] Azure
- [x] GCP
- [x] IBM
## Does this introduce a breaking change?
- [YES]
## What is the current behavior?
Provides info about maven build and git
# Other comments:
Fetching `connectedOuterServices` information with service-specific values not implemented for actual MRM7 - Release 0.10Rostislav Dublin (EPAM)Rostislav Dublin (EPAM)https://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/merge_requests/103Added new version info endpoint (GONRG-2681)2022-09-16T08:51:38ZDmitrii Novikov (EPAM)Added new version info endpoint (GONRG-2681)## Type of change
- [ ] Bug Fix
- [x] Feature
osdu/platform/system/lib/core/os-core-common#47
## Does this introduce a change in the core logic?
- [YES]
## Does this introduce a change in the cloud provider implementation, if so whic...## Type of change
- [ ] Bug Fix
- [x] Feature
osdu/platform/system/lib/core/os-core-common#47
## Does this introduce a change in the core logic?
- [YES]
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [x] AWS
- [x] Azure
- [x] GCP
- [x] IBM
## Does this introduce a breaking change?
- [YES]
## What is the current behavior?
Provides info about maven build and gitM7 - Release 0.10Rostislav Dublin (EPAM)Rostislav Dublin (EPAM)https://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/merge_requests/73partion-service-as-tenantinfo-provider (GONRG-2188)2023-08-18T13:08:12ZRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.compartion-service-as-tenantinfo-provider (GONRG-2188)# Description:
Replace TenantInfo table call in os-core-common with implementation that utilize Partition Service <br/>
Migration of OSDU Core R3 services to Partition service<br/>
# How to test:
Functionality was tested with Schema se...# Description:
Replace TenantInfo table call in os-core-common with implementation that utilize Partition Service <br/>
Migration of OSDU Core R3 services to Partition service<br/>
# How to test:
Functionality was tested with Schema service , that successfully consume TenantInfo from Partition Service
# Changes include:
- [ ] Refactor (a non-breaking change that improves code maintainability).
- [ ] 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] Common code
# 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.
# Other comments:
Partition service must have configured TenantInfo according to common model:<br/>
Long id;<br/>
String name;<br/>
String projectId;<br/>
String serviceAccount;<br/>
String complianceRuleSet;<br/>
String dataPartitionId;<br/>
List<String> crmAccountIds;<br/>M6 - Release 0.9Rostislav Dublin (EPAM)Rostislav Dublin (EPAM)https://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/merge_requests/52Fix multi record info2023-08-18T13:08:38ZMatt WiseFix multi record infoNo existing core service uses MultiRecordInfo that I have seen. Therefore, should be a non-breaking fix
The IStorageService implementation in core was returning Strings rather than Records for the query records route. Other Record quer...No existing core service uses MultiRecordInfo that I have seen. Therefore, should be a non-breaking fix
The IStorageService implementation in core was returning Strings rather than Records for the query records route. Other Record query interfaces use the Record object.
The implementation was also throwing two different Exceptions that are resolved by this MR.
It appears the function was broken during the change to use the new BodyMapper, but went unnoticed until now.M3 - Release 0.5ethiraj krishnamanaiduJoeethiraj krishnamanaiduhttps://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/merge_requests/38Url normalization (GONRG-1211)2023-08-18T13:08:53ZRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comUrl normalization (GONRG-1211)# Description:
Service endpoints receiving with simple string joining
`return StringUtils.join(this.rootUrl, pathAndQuery);`
makes service configuration more complex,
it leads to issues related to root url value.
Service endpoint rece...# Description:
Service endpoints receiving with simple string joining
`return StringUtils.join(this.rootUrl, pathAndQuery);`
makes service configuration more complex,
it leads to issues related to root url value.
Service endpoint receiving was changed from simple string concatenation
to URL normalization.
# Changes include:
- [x] Refactor (a non-breaking change that improves code maintainability).
- [x] Bugfix (a non-breaking change that solves an issue).
- [ ] 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] GCP
- [x] Azure
- [x] AWS
- [x] 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.M1 - Release 0.1Rostislav Dublin (EPAM)Rostislav Dublin (EPAM)