Search merge requestshttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests2023-03-23T18:49:27Zhttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/447Use VMCache instead of map in memory to cache the index aliases2023-03-23T18:49:27ZZhibin MaiUse VMCache instead of map in memory to cache the index aliases## 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]
## Does this introduce a change in the cloud prov...## 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]
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [x] Azure
- [ ] Google Cloud
- [ ] IBM
## Does this introduce a breaking change?
- [NO]
## What is the current behavior?
The index alias is cached in memory Map. The cache of the aliases is not partition-safe
## What is the new/expected behavior?
The index alias is cached in VMCache. The cache of the aliases is partition-safe.
## Have you added/updated Unit Tests and Integration Tests?
Yes
## Any other useful informationM17 - Release 0.20Neelesh ThakurZhibin MaiNeelesh Thakurhttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/445Added policy error handling (GONRG-6457)2023-03-23T18:53:41ZYurii Ruban [EPAM / GCP]Added policy error handling (GONRG-6457)# Description:
Added policy error handling in core common library. Also, the lib version was updated in the search service.
Issue: https://community.opengroup.org/osdu/platform/system/search-service/-/issues/120 .
The bug reason: in the...# Description:
Added policy error handling in core common library. Also, the lib version was updated in the search service.
Issue: https://community.opengroup.org/osdu/platform/system/search-service/-/issues/120 .
The bug reason: in the case of receiving an error from the service policy, the error was not handled and the program continued to execute the next steps of the request.
Solution: handle the error from the policy service. Also, the error message was added.
# How to test:
Does functionality was tested and how?
# Changes include:
- [x] Bugfix (a non-breaking change that solves an issue).
# Changes in:
- [x] GCP
- [x] Azure
- [x] AWS
- [x] IBMM17 - Release 0.20Riabokon Stanislav(EPAM)[GCP]Riabokon Stanislav(EPAM)[GCP]https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/444Merge branch 'aws-integration-merge-estepamo' into 'master'2023-02-26T18:08:44ZMorris EstepaMerge branch 'aws-integration-merge-estepamo' into 'master'Original MR: !443
Merge fix where search service fails when data partition id in kind contains a hyphen.Original MR: !443
Merge fix where search service fails when data partition id in kind contains a hyphen.M16 - Release 0.19David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/443Fix issue where hyphen in kind name causes search to fail2023-02-23T03:21:53ZMorris EstepaFix issue where hyphen in kind name causes search to fail## 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
- [ ] Google Cloud
- [ ] IBM
## Does this introduce a breaking change?
- [NO]
## What is the current behavior?
Search is failing when searching a kind where the data partition id contains a hyphen (e.g. "partition-id-name:*:*:*")
## What is the new/expected behavior?
Search completes successfully
## 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/search-service/-/merge_requests/442Merge branch 'aws-integration-merge-estepamo' into 'master'2023-02-22T16:08:48ZMorris EstepaMerge branch 'aws-integration-merge-estepamo' into 'master'Original MR: !440Original MR: !440M16 - Release 0.19David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/441Cherry-pick 'Fix issue where users could not search using hundreds of kinds a...2023-02-21T17:42:08ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Fix issue where users could not search using hundreds of kinds at once' into release/0.19**Original MR**: !440
### 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**: !440
### 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/search-service/-/pipelines/new?ref=cherry-pick-for-440)M16 - Release 0.19David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/440Fix issue where users could not search using hundreds of kinds at once2023-02-21T21:24:45ZMorris EstepaFix issue where users could not search using hundreds of kinds at once## 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
- [ ] Google Cloud
- [ ] IBM
## Does this introduce a breaking change?
- [NO]
## What is the current behavior?
Searching using hundreds of kinds at once in AWS is failing.
## What is the new/expected behavior?
Search service will search using index aliases when the list of kinds are too long
## 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/search-service/-/merge_requests/439Cherry-pick 'Remove SNAPSHOT dependencies' into release/0.192023-02-18T07:29:34ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Remove SNAPSHOT dependencies' into release/0.19**Original MR**: !438
### 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**: !438
### 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/search-service/-/pipelines/new?ref=cherry-pick-for-438)M16 - Release 0.19David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/438Remove SNAPSHOT dependencies2023-02-18T07:29:33ZDavid Diederichd.diederich@opengroup.orgRemove SNAPSHOT dependenciesThis automated MR removes usage of `SNAPSHOT` versions in the first party library dependencies.
Since `SNAPSHOT` dependencies change frequently -- by their nature -- usage of them across projects is dangerous and should be avoided.
### ...This automated MR removes usage of `SNAPSHOT` versions in the first party library dependencies.
Since `SNAPSHOT` dependencies change frequently -- by their nature -- usage of them across projects is dangerous and should be avoided.
### Dependency Information Before the Upgrade
```
Branch: master
SHA: e47d7fedf8194150afb97b85c0f54a6c9becf012
Maven: 0.20.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/integration-tests/ |
| ------------------------------------------------------- | ---------------- | -------------------------- |
| core-lib-azure | 0.17.0 | 0.13.0-rc6 |
| core-lib-gcp | 0.19.0-rc3 | |
| os-core-lib-aws | 0.18.0 | 0.14.0-rc2 |
| obm | 0.18.0 | |
| oqm | 0.18.0 | |
| os-core-common | 0.19.0-SNAPSHOT | 0.18.0 |
| os-core-lib-ibm | 0.16.0-rc1 | 0.15.2 |
| osm | 0.18.0 | |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.13.2.2, 2.14.0 | 2.13.2.2 |
| (3rd Party) org.apache.logging.log4j.log4j-api | 2.17.1 | 2.11.1, 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-core | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-jul | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-slf4j-impl | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-to-slf4j | 2.17.1 | 2.11.2 |
| (3rd Party) org.springframework.spring-webflux | 5.3.22 | |
| (3rd Party) org.springframework.spring-webmvc | 5.3.24, 5.3.22 | 5.3.22 |
### Dependency Information After the Upgrade
```
Branch: dependency-upgrade-4
SHA: cd4e65744aeaae9200184b74272083703b626a5c
Maven: 0.20.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/integration-tests/ |
| ------------------------------------------------------- | ---------------- | -------------------------- |
| core-lib-azure | 0.17.0 | 0.13.0-rc6 |
| core-lib-gcp | 0.19.0-rc3 | |
| os-core-lib-aws | 0.18.0 | 0.14.0-rc2 |
| obm | 0.18.0 | |
| oqm | 0.18.0 | |
| os-core-common | 0.19.0 | 0.19.0 |
| os-core-lib-ibm | 0.16.0-rc1 | 0.15.2 |
| osm | 0.18.0 | |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.13.2.2, 2.14.0 | 2.13.2.2 |
| (3rd Party) org.apache.logging.log4j.log4j-api | 2.17.1 | 2.11.1, 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-core | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-jul | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-slf4j-impl | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-to-slf4j | 2.17.1 | 2.11.2 |
| (3rd Party) org.springframework.spring-webflux | 5.3.22 | |
| (3rd Party) org.springframework.spring-webmvc | 5.3.24, 5.3.22 | 5.3.22 |M16 - Release 0.19https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/437Security upgrade2023-03-17T14:52:04ZYash DholakiaSecurity upgrade## 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
- [ ] Google Cloud
- [ ] 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 informationM17 - Release 0.20Yash DholakiaYash Dholakiahttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/436Vul fix ibm search service2023-03-30T08:07:19ZPintu GuptaVul fix ibm search serviceFollowing CVE has been fix with this MR :
| cve | link |
|-----|------|
| CVE-2022-25857 | https://nvd.nist.gov/vuln/detail/CVE-2022-25857 |
| CVE-2022-42003 | https://nvd.nist.gov/vuln/detail/CVE-2022-42003 |
| CVE-2022-42004 | https://...Following CVE has been fix with this MR :
| cve | link |
|-----|------|
| CVE-2022-25857 | https://nvd.nist.gov/vuln/detail/CVE-2022-25857 |
| CVE-2022-42003 | https://nvd.nist.gov/vuln/detail/CVE-2022-42003 |
| CVE-2022-42004 | https://nvd.nist.gov/vuln/detail/CVE-2022-42004 |
| CVE-2021-36090 | https://nvd.nist.gov/vuln/detail/CVE-2021-36090 |
| CVE-2022-42252 | https://nvd.nist.gov/vuln/detail/CVE-2022-42252 |M17 - Release 0.20Pintu GuptaPintu Guptahttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/435GONRG-6470: Update requests according to vpa2023-02-20T11:54:40ZYurii Pelykh [EPAM / GCP]GONRG-6470: Update requests according to vpa- Resources requests updated according to VPA recommendations.- Resources requests updated according to VPA recommendations.M17 - Release 0.20Yurii Pelykh [EPAM / GCP]Yurii Pelykh [EPAM / GCP]https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/434Cherry-pick 'Use alias to shorten the index names in multi-kind searchMulti k...2023-02-14T07:53:50ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Use alias to shorten the index names in multi-kind searchMulti kind alias' into release/0.19**Original MR**: !423
### 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**: !423
### 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/search-service/-/pipelines/new?ref=cherry-pick-for-423)M16 - Release 0.19David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/433AWS: Security vulnerability fixes2023-03-19T12:53:36ZYash DholakiaAWS: Security vulnerability fixes## 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
- [ ] Google Cloud
- [ ] IBM
## Does this introduce a breaking change?
- [NO]
## What is the current behavior?
Spring-security-core version below 5.7.5
## What is the new/expected behavior?
Spring-security-core version abobe 5.7.5 and other security package upgrades
## Have you added/updated Unit Tests and Integration Tests?
## Any other useful informationM17 - Release 0.20https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/432Cherry-pick 'adding support for EKS 1.23' into release/0.192023-02-11T01:58:39ZMarc Burnie [AWS]Cherry-pick 'adding support for EKS 1.23' into release/0.19Original MR: https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/431
Only AWS Helm Chart changesOriginal MR: https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/431
Only AWS Helm Chart changesM16 - Release 0.19David Diederichd.diederich@opengroup.orgMarc Burnie [AWS]David Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/431Adding support for EKS 1.232023-02-10T21:28:18ZMarc Burnie [AWS]Adding support for EKS 1.23M16 - Release 0.19Marc Burnie [AWS]Marc Burnie [AWS]https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/430Security Fixes2023-03-17T14:51:53ZMarc Burnie [AWS]Security FixesM17 - Release 0.20Marc Burnie [AWS]Marc Burnie [AWS]https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/429GONRG-6443: Remove configmap jobs and variables2023-02-20T11:55:39ZYurii Pelykh [EPAM / GCP]GONRG-6443: Remove configmap jobs and variables- Configmap variable `GC_ENABLE_HELM_CONFIG` removed as unused anymore.- Configmap variable `GC_ENABLE_HELM_CONFIG` removed as unused anymore.M17 - Release 0.20Yurii Pelykh [EPAM / GCP]Yurii Pelykh [EPAM / GCP]https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/428Adding support for EKS 1.232023-02-10T18:11:19ZMarc Burnie [AWS]Adding support for EKS 1.23M16 - Release 0.19Marc Burnie [AWS]Marc Burnie [AWS]https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/427Upgrade First Party Library Dependencies for Release 0.192023-02-18T07:31:16ZDavid Diederichd.diederich@opengroup.orgUpgrade First Party Library Dependencies for Release 0.19This 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: e136c36ae0f5b25769df441fb839a3c9a194b7a0
Maven: 0.20.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/integration-tests/ |
| ------------------------------------------------------- | -------------------------- | -------------------------- |
| core-lib-azure | 0.17.0 | 0.13.0-rc6 |
| core-lib-gcp | 0.19.0-rc3 | |
| os-core-lib-aws | 0.18.0 | 0.14.0-rc2 |
| obm | 0.18.0 | |
| oqm | 0.18.0 | |
| os-core-common | 0.18.0, 0.17.0, 0.19.0-rc6 | 0.18.0 |
| os-core-lib-ibm | 0.16.0-rc1 | 0.15.2 |
| osm | 0.18.0 | |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.13.2.2 | 2.13.2.2 |
| (3rd Party) org.apache.logging.log4j.log4j-api | 2.17.1 | 2.11.1, 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-core | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-jul | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-slf4j-impl | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-to-slf4j | 2.17.1 | 2.11.2 |
| (3rd Party) org.springframework.spring-webflux | 5.3.22 | |
| (3rd Party) org.springframework.spring-webmvc | 5.3.22 | 5.3.22 |
### Dependency Information After the Upgrade
```
Branch: dependency-upgrade-3
SHA: bf7c0771f00f76ec7699f810168a2417a8dcdb47
Maven: 0.20.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/integration-tests/ |
| ------------------------------------------------------- | -------------- | -------------------------- |
| core-lib-azure | 0.17.0 | 0.13.0-rc6 |
| core-lib-gcp | 0.19.0 | |
| os-core-lib-aws | 0.19.0 | 0.14.0-rc2 |
| obm | 0.19.0 | |
| oqm | 0.19.0 | |
| os-core-common | 0.19.0, 0.17.0 | 0.19.0 |
| os-core-lib-ibm | 0.16.0-rc1 | 0.15.2 |
| osm | 0.19.0 | |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.13.2.2 | 2.13.2.2 |
| (3rd Party) org.apache.logging.log4j.log4j-api | 2.17.1 | 2.11.1, 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-core | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-jul | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-slf4j-impl | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-to-slf4j | 2.17.1 | 2.11.2 |
| (3rd Party) org.springframework.spring-webflux | 5.3.22 | |
| (3rd Party) org.springframework.spring-webmvc | 5.3.24, 5.3.22 | 5.3.22 |M16 - Release 0.19