Dataset merge requestshttps://community.opengroup.org/osdu/platform/system/dataset/-/merge_requests2024-03-28T13:26:51Zhttps://community.opengroup.org/osdu/platform/system/dataset/-/merge_requests/441AWS - Define the log level for http.wire to avoid logging of credentials in t...2024-03-28T13:26:51ZGuillaume CailletAWS - Define the log level for http.wire to avoid logging of credentials in the Pipeline logs## 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?
AWS Change only.
Integrations tests logs are too verbose and dump the raw http requests, with their payload.
This could lead to leaked credentials.M23 - Release 0.26Guillaume CailletGuillaume Caillethttps://community.opengroup.org/osdu/platform/system/dataset/-/merge_requests/429Update lib2024-03-19T17:10:26ZRucha DeshpandeUpdate lib## 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 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?
- [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 informationM23 - Release 0.26https://community.opengroup.org/osdu/platform/system/dataset/-/merge_requests/423Resolve AWS internal scanned CVE2024-01-24T22:17:17ZBruce JinResolve AWS internal scanned CVE## 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 information
Resolve AWS internal trivy scan CVE, will need to skip `logback` related CVEs since these need to be solved after Spring 6.0 upgradeM23 - Release 0.26Bruce JinBruce Jinhttps://community.opengroup.org/osdu/platform/system/dataset/-/merge_requests/422Aws fix cve2024-01-23T16:23:37ZBruce JinAws fix cve## 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?
- [x] AWS
- [ ] Azure
- [ ] Google Cloud
- [ ] IBM
## Does this introduce a breaking change?
- [NO]
## What is the current behavior?
Existing Vulnerability fix
https://community.opengroup.org/osdu/platform/system/dataset/-/issues/75
https://community.opengroup.org/osdu/platform/system/dataset/-/issues/65
https://community.opengroup.org/osdu/platform/system/dataset/-/issues/66
https://community.opengroup.org/osdu/platform/system/dataset/-/issues/67
https://community.opengroup.org/osdu/platform/system/dataset/-/issues/68
## What is the new/expected behavior?
## Have you added/updated Unit Tests and Integration Tests?
## Any other useful informationM23 - Release 0.26Bruce JinBruce Jinhttps://community.opengroup.org/osdu/platform/system/dataset/-/merge_requests/411Cherry-pick 'Full Upgrade of First Party Library Dependencies for Release 0.2...2023-12-16T10:25:42ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Full Upgrade of First Party Library Dependencies for Release 0.25' into release/0.25**Original MR**: !410
### 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**: !410
### 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/dataset/-/pipelines/new?ref=cherry-pick-for-410)M22 - Release 0.25David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/dataset/-/merge_requests/410Full Upgrade of First Party Library Dependencies for Release 0.252023-12-15T20:04:49ZDavid Diederichd.diederich@opengroup.orgFull Upgrade of First Party Library Dependencies for Release 0.25This 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: f34e353710eeb578fefd5f978ea76c514486f9e1
Maven: 0.26.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------------------------------------------- | ------------------ | ------------------------ |
| apd-core | 0.24.0-rc1 | |
| core-lib-azure | 0.25.0-rc2 | 0.24.0 |
| core-lib-gc | 0.24.0 | 0.24.0 |
| core-plus-common-lib | 0.24.0-rc3 | |
| os-core-lib-aws | 0.25.0-rc3 | 0.25.0-rc3 |
| obm | | 0.24.0 |
| oqm | 0.24.0 | |
| os-core-common | 0.25.0-rc2, 0.24.0 | 0.25.0-rc2, 0.24.0 |
| os-core-lib-ibm | 0.24.0 | 0.24.0 |
| os-osm-core | 0.25.0-rc2 | |
| osm | 0.24.0 | |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.13.4.2 | 2.13.2.2, 2.13.0, 2.12.2 |
| (3rd Party) org.yaml.snakeyaml | 2.0 | 1.30, 1.27, 2.0 |
### Dependency Information After the Upgrade
```
Branch: dependency-upgrade
SHA: 4e41b80785222ab104c0d16cfe41afa7df556c51
Maven: 0.26.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------------------------------------------- | -------- | ------------------------ |
| core-lib-azure | 0.25.0 | 0.25.0 |
| core-lib-gc | 0.25.0 | 0.25.0 |
| os-core-lib-aws | 0.25.0 | 0.25.0 |
| obm | | 0.25.0 |
| oqm | 0.25.0 | |
| os-core-common | 0.25.0 | 0.25.0 |
| os-core-lib-ibm | 0.25.0 | 0.25.0 |
| osm | 0.25.0 | |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.13.4.2 | 2.13.2.2, 2.13.0, 2.12.2 |
| (3rd Party) org.yaml.snakeyaml | 2.0 | 1.30, 1.27, 2.0 |M22 - Release 0.25https://community.opengroup.org/osdu/platform/system/dataset/-/merge_requests/402update os-core-common in testing projects2023-12-07T14:06:47ZSolomon Ayalewupdate os-core-common in testing projects## Type of change
- [ ] 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
- [ ] 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?
- [ ] 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 informationM22 - Release 0.25https://community.opengroup.org/osdu/platform/system/dataset/-/merge_requests/401update os-core-lib-aws2023-12-05T20:49:39ZYunhua Koglinupdate os-core-lib-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?
- [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?
- [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 informationM22 - Release 0.25Yunhua KoglinYunhua Koglinhttps://community.opengroup.org/osdu/platform/system/dataset/-/merge_requests/399pull latest version os-core-common2023-12-01T17:57:55ZSolomon Ayalewpull latest version os-core-common## Type of change
- [ ] 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
- [ ] 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?
- [ ] AWS
- [ ] Azure
- [ ] Google Cloud
- [ ] IBM
## Does this introduce a breaking change?
- [NO]
## What is the current behavior?
## What is the new/expected behavior?
same as old
## Have you added/updated Unit Tests and Integration Tests?
Not applicable
## Any other useful informationM22 - Release 0.25https://community.opengroup.org/osdu/platform/system/dataset/-/merge_requests/397Fix compile issues by relying on an increased version number.2023-11-30T02:59:28ZDerek HudsonFix compile issues by relying on an increased version number.## 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?
Fails to compile.
## What is the new/expected behavior?
Fixes compilation.
## Have you added/updated Unit Tests and Integration Tests?
N/A
## Any other useful informationM22 - Release 0.25Yong ZengDerek HudsonYong Zenghttps://community.opengroup.org/osdu/platform/system/dataset/-/merge_requests/396AWS - Merge from dev2023-11-27T19:18:10ZGuillaume CailletAWS - Merge from devAWS only
* Add or update License header
* Upgrade buildspecAWS only
* Add or update License header
* Upgrade buildspecM22 - Release 0.25Guillaume CailletGuillaume Caillethttps://community.opengroup.org/osdu/platform/system/dataset/-/merge_requests/391Added a new endpoint /liveness_check (GONRG-7901)2023-11-10T08:47:50ZRiabokon Stanislav(EPAM)[GCP]Added a new endpoint /liveness_check (GONRG-7901)## Type of change
- [ ] Bug Fix
- [x] Feature
https://community.opengroup.org/osdu/platform/system/dataset/-/issues/63
## Does this introduce a change in the core logic?
- [YES]
## Does this introduce a change in the cloud provider i...## Type of change
- [ ] Bug Fix
- [x] Feature
https://community.opengroup.org/osdu/platform/system/dataset/-/issues/63
## 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] Google Cloud
- [x] IBM
## Does this introduce a breaking change?
- [NO]
## What is the new/expected behavior?
A new endpoint /liveness_check.M22 - Release 0.25Riabokon Stanislav(EPAM)[GCP]Riabokon Stanislav(EPAM)[GCP]https://community.opengroup.org/osdu/platform/system/dataset/-/merge_requests/388Address Spring Security Vulnerability - CVE-2023-208622023-11-03T13:49:33ZSolomon AyalewAddress Spring Security Vulnerability - CVE-2023-20862## Type of change
- [ ] Bug Fix
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
https://community.opengroup.org/osdu/platform/security-and-compliance/home/-/issues/160
## Does this introduce a change in ...## Type of change
- [ ] Bug Fix
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
https://community.opengroup.org/osdu/platform/security-and-compliance/home/-/issues/160
## Does this introduce a change in the core logic?
- [NO]
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [NO]
## Does this introduce a breaking change?
- [NO]
## What is the current behavior?
## What is the new/expected behavior?
- same as old
## Have you added/updated Unit Tests and Integration Tests?
- No
## Any other useful information
- This is just version upgrade of maven dependancies.M22 - Release 0.25https://community.opengroup.org/osdu/platform/system/dataset/-/merge_requests/390Update spring-boot-dependencies version and cleanup version specific override...2023-11-03T13:38:26ZSolomon AyalewUpdate spring-boot-dependencies version and cleanup version specific override to avoid downgrading version## Type of change
- [X] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
https://community.opengroup.org/osdu/platform/security-and-compliance/home/-/issues/160
## Does this introduc...## Type of change
- [X] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
https://community.opengroup.org/osdu/platform/security-and-compliance/home/-/issues/160
## 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
- [ ] Google Cloud
- [ ] IBM
## Does this introduce a breaking change?
- [NO]
## What is the current behavior?
## What is the new/expected behavior?
same as old
## Have you added/updated Unit Tests and Integration Tests?
NO
## Any other useful informationM22 - Release 0.25https://community.opengroup.org/osdu/platform/system/dataset/-/merge_requests/389mitigate CVE-2023-34034 and metigate CVE-2023-20862 from dependencies2023-11-01T15:38:50ZSolomon Ayalewmitigate CVE-2023-34034 and metigate CVE-2023-20862 from dependencies## Type of change
- [x] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
https://community.opengroup.org/osdu/platform/security-and-compliance/home/-/issues/160
## Does this introduc...## Type of change
- [x] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
https://community.opengroup.org/osdu/platform/security-and-compliance/home/-/issues/160
## Does this introduce a change in the core logic?
- [NO]
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [No] AWS
- [No] Azure
- [No] Google Cloud
- [No] IBM
## Does this introduce a breaking change?
- [NO]
## What is the current behavior?
## What is the new/expected behavior?
same as the old
## Have you added/updated Unit Tests and Integration Tests?
No
## Any other useful information
https://mvnrepository.com/artifact/org.springframework.security/spring-security-config/5.7.6
https://mvnrepository.com/artifact/org.springframework.security/spring-security-oauth2-client/5.7.5M22 - Release 0.25https://community.opengroup.org/osdu/platform/system/dataset/-/merge_requests/387Cherry-pick 'Java 17 Migration' into release/0.242023-10-19T11:12:25ZChad LeongCherry-pick 'Java 17 Migration' into release/0.24**Original MR**: !378
### 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**: !378
### 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/dataset/-/pipelines/new?ref=cherry-pick-for-378)M21 - Release 0.24David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/dataset/-/merge_requests/386Cherry-pick 'Upgrade First Party Library Dependencies for Release 0.24' into ...2023-10-19T10:47:59ZChad LeongCherry-pick 'Upgrade First Party Library Dependencies for Release 0.24' into release/0.24**Original MR**: !384
### 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**: !384
### 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/dataset/-/pipelines/new?ref=cherry-pick-for-384)M21 - Release 0.24David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/dataset/-/merge_requests/384Upgrade First Party Library Dependencies for Release 0.242023-10-27T10:47:33ZChad LeongUpgrade First Party Library Dependencies for Release 0.24This generated 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 generated 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: 3284c47e512dfa7c3465c6c70240994515512b83
Maven: 0.25.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------------------ | ---------- | -------- |
| os-core-common | 0.24.0-rc2 | 0.23.3 |
| (3rd Party) org.yaml.snakeyaml | 2.0 | 1.30 |
### Dependency Information After the Upgrade
```
Branch: dependency-upgrade-2
SHA: f1b2fe30412292d4b0d5f440ecd47ec47c87c73b
Maven: 0.25.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------------------ | ------ | -------- |
| core-lib-azure | 0.24.0 | |
| core-lib-gc | 0.24.0 | |
| os-core-lib-aws | 0.24.0 | |
| oqm | 0.24.0 | |
| os-core-common | 0.24.0 | 0.24.0 |
| os-core-lib-ibm | 0.24.0 | |
| osm | 0.24.0 | |
| (3rd Party) org.yaml.snakeyaml | 2.0 | 1.30 |M21 - Release 0.24https://community.opengroup.org/osdu/platform/system/dataset/-/merge_requests/378Java 17 Migration2024-01-25T13:47:34ZThulasi Dass SubramanianJava 17 Migration# Description:
* Migration from Java 8 to Java 17.
* Unit test fixes with build run args and dependency upgrades.
* For Integration Test - Refactored with Apache's `CloseableHttpClient` which supports all HTTP methods (include PATCH).
...# Description:
* Migration from Java 8 to Java 17.
* Unit test fixes with build run args and dependency upgrades.
* For Integration Test - Refactored with Apache's `CloseableHttpClient` which supports all HTTP methods (include PATCH).
# How to test:
Via Unit and Integration tests.
# Changes include:
* [x] Breaking change (a change that is not backward-compatible and/or changes current functionality).
# Changes in:
* [x] Common code
# Dev Checklist:
* [ ] Added Unit Tests, wherever applicable.
* [x] Updated the Readme, if applicable.
* [x] Existing Tests pass
* [x] Verified functionality locally
* [ ] Self Reviewed my code for formatting and complex business logic.
# Other comments:
* Upgraded 'lombok' & 'jacoco' plugin version
* Integration test: Jersey HttpClient to support PATCH method, uses `reflection` logic which will not work in JDK 17. Hence replaced with Apache Apache's `CloseableHttpClient`.M21 - Release 0.24Thulasi Dass SubramanianThulasi Dass Subramanianhttps://community.opengroup.org/osdu/platform/system/dataset/-/merge_requests/380merge code to gitlab2023-10-13T14:03:22ZYunhua Koglinmerge code to gitlab## 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 information
add unit tests for awsM21 - Release 0.24Derek HudsonDerek Hudson