OSM merge requestshttps://community.opengroup.org/osdu/platform/system/lib/cloud/gcp/osm/-/merge_requests2024-02-27T10:40:50Zhttps://community.opengroup.org/osdu/platform/system/lib/cloud/gcp/osm/-/merge_requests/60break circular dependency between spring beans(GONRG-9301)2024-02-27T10:40:50ZRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.combreak circular dependency between spring beans(GONRG-9301)# Description:
- Break circular dependency between spring beans.
- Added Partition Service mock to bare-metal tests.
# How to test:
Does functionality was tested and how?
# Changes include:
- [ ] Refactor (a non-breaking change that...# Description:
- Break circular dependency between spring beans.
- Added Partition Service mock to bare-metal tests.
# How to test:
Does functionality was tested and how?
# Changes include:
- [ ] 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] GC
# Dev Checklist:
- [ ] Added Unit Tests, wherever applicable.
- [ ] Updated the Readme, if applicable.
- [ ] Existing Tests pass
- [ ] Verified functionality locally
- [ ] Self Reviewed my code for formatting and complex business logic.M23 - Release 0.26Rustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comhttps://community.opengroup.org/osdu/platform/system/lib/cloud/gcp/osm/-/merge_requests/59Added database id to datastore configuration2023-12-21T11:56:36ZRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comAdded database id to datastore configuration# Description:
Added support for Google Datastore Database ID selection https://cloud.google.com/datastore/docs/manage-databases
# How to test:
via integration tests
# Changes include:
- [ ] Refactor (a non-breaking change that impro...# Description:
Added support for Google Datastore Database ID selection https://cloud.google.com/datastore/docs/manage-databases
# How to test:
via integration tests
# 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] Google Cloud
- [ ] Azure
- [ ] AWS
- [ ] IBM
# Dev Checklist:
- [ ] 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.M23 - Release 0.26Rustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comhttps://community.opengroup.org/osdu/platform/system/lib/cloud/gcp/osm/-/merge_requests/58Cherry-pick 'Full Upgrade of First Party Library Dependencies' into release/0.252023-12-12T19:21:40ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Full Upgrade of First Party Library Dependencies' into release/0.25**Original MR**: !57
### 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 incorporatin...**Original MR**: !57
### 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/cloud/gcp/osm/-/pipelines/new?ref=cherry-pick-for-57)M22 - Release 0.25David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/lib/cloud/gcp/osm/-/merge_requests/57Full Upgrade of First Party Library Dependencies2023-12-12T18:04:18ZDavid Diederichd.diederich@opengroup.orgFull Upgrade of First Party Library DependenciesThis generated MR upgrades the first party libraries (other OSDU libraries) to utilize the latest release.
The intent is to keep all dependent libraries up to date.
This upgrade can be merged immediately without further approval if the C...This generated MR upgrades the first party libraries (other OSDU libraries) to utilize the latest release.
The intent is to keep all dependent libraries up to date.
This upgrade can be merged immediately without further approval if the CI pipeline reports success.
If this MR has failed, we need to work with the maintainers and affected provider teams to find a solution.
### Dependency Information Before the Upgrade
```
Branch: main
SHA: 09898c424730d701659ebea0634d6daf2185fec0
Maven: 0.26.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------ | ------ | -------- |
| os-core-common | 0.24.0 | 0.24.0 |
### Dependency Information After the Upgrade
```
Branch: dependency-upgrade
SHA: 37cc00af38270e6ff09d31159ab5a7cce707fad0
Maven: 0.26.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------ | ------ | -------- |
| os-core-common | 0.25.0 | 0.25.0 |M22 - Release 0.25https://community.opengroup.org/osdu/platform/system/lib/cloud/gcp/osm/-/merge_requests/56Update FOSSA NOTICE2023-12-08T20:36:29ZDavid Diederichd.diederich@opengroup.orgUpdate FOSSA NOTICEThis MR updates the attribution file for the project (also known as the `NOTICE` file).
It is important to keep this up to date to satisfy legal requirements of dependency licenses.
We use FOSSA as the tool to scan for and detect these ...This MR updates the attribution file for the project (also known as the `NOTICE` file).
It is important to keep this up to date to satisfy legal requirements of dependency licenses.
We use FOSSA as the tool to scan for and detect these changes.M22 - Release 0.25https://community.opengroup.org/osdu/platform/system/lib/cloud/gcp/osm/-/merge_requests/55Upgrade First Party Library Dependencies for Release 0.242023-10-13T18:09:02ZDavid Diederichd.diederich@opengroup.orgUpgrade 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: main
SHA: 633d5de19519a8a78ac08869c2f90097fbc2a7df
Maven: 0.24.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------ | ------ | -------- |
| os-core-common | 0.23.0 | 0.23.0 |
### Dependency Information After the Upgrade
```
Branch: dependency-upgrade
SHA: de7a08812c81d5443b6908db59a90eed9065654a
Maven: 0.24.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------ | ------ | -------- |
| os-core-common | 0.24.0 | 0.24.0 |M21 - Release 0.24https://community.opengroup.org/osdu/platform/system/lib/cloud/gcp/osm/-/merge_requests/54Cherry-pick 'Upgrade First Party Library Dependencies for Release 0.23' into ...2023-10-13T18:02:34ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Upgrade First Party Library Dependencies for Release 0.23' into release/0.23**Original MR**: !53
### 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 incorporatin...**Original MR**: !53
### 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/cloud/gcp/osm/-/pipelines/new?ref=cherry-pick-for-53)M20 - Release 0.23David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/lib/cloud/gcp/osm/-/merge_requests/53Upgrade First Party Library Dependencies for Release 0.232023-10-13T18:02:32ZDavid Diederichd.diederich@opengroup.orgUpgrade First Party Library Dependencies for Release 0.23This 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: main
SHA: 837027db41c8e47233372c96d08f50de981c58b1
Maven: 0.24.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------ | ------ | -------- |
| os-core-common | 0.22.0 | 0.22.0 |
### Dependency Information After the Upgrade
```
Branch: dependency-upgrade
SHA: c8c6a4ea068f194c6b6ca5b9b6f1200f4b714dde
Maven: 0.24.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------ | ------ | -------- |
| os-core-common | 0.23.0 | 0.23.0 |M20 - Release 0.23https://community.opengroup.org/osdu/platform/system/lib/cloud/gcp/osm/-/merge_requests/52Cherry-pick 'Upgrade First Party Library Dependencies for Release 0.22' into ...2023-07-12T07:28:52ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Upgrade First Party Library Dependencies for Release 0.22' into release/0.22**Original MR**: !51
### 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 incorporatin...**Original MR**: !51
### 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/cloud/gcp/osm/-/pipelines/new?ref=cherry-pick-for-51)M19 - Release 0.22David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/lib/cloud/gcp/osm/-/merge_requests/51Upgrade First Party Library Dependencies for Release 0.222023-07-11T21:00:36ZDavid Diederichd.diederich@opengroup.orgUpgrade First Party Library Dependencies for Release 0.22This 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: main
SHA: db7b40aadb8b485fcc80dc48873cc2bba9dfc636
Maven: 0.23.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------ | ------ | -------- |
| os-core-common | 0.21.0 | 0.21.0 |
### Dependency Information After the Upgrade
```
Branch: dependency-upgrade-2
SHA: 9ffb1e042a2ebf48363ada7db3eb1c8b9516102d
Maven: 0.23.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------ | ------ | -------- |
| os-core-common | 0.22.0 | 0.22.0 |M19 - Release 0.22https://community.opengroup.org/osdu/platform/system/lib/cloud/gcp/osm/-/merge_requests/50Test Partition properties2023-06-14T16:39:18ZDmitrii Novikov (EPAM)Test Partition propertiesReplaced env vars with partition properties for int testsReplaced env vars with partition properties for int testsM19 - Release 0.22Dmitrii Novikov (EPAM)Dmitrii Novikov (EPAM)https://community.opengroup.org/osdu/platform/system/lib/cloud/gcp/osm/-/merge_requests/49Fixed CVE-2022-21724 (GONRG-7203)2023-05-26T14:15:07ZRiabokon Stanislav(EPAM)[GCP]Fixed CVE-2022-21724 (GONRG-7203)Fixed CVE-2022-21724
Issue: https://community.opengroup.org/osdu/platform/system/lib/cloud/gcp/osm/-/security/vulnerabilities/18626
https://community.opengroup.org/osdu/platform/security-and-compliance/home/-/issues/173Fixed CVE-2022-21724
Issue: https://community.opengroup.org/osdu/platform/system/lib/cloud/gcp/osm/-/security/vulnerabilities/18626
https://community.opengroup.org/osdu/platform/security-and-compliance/home/-/issues/173M19 - Release 0.22Riabokon Stanislav(EPAM)[GCP]Riabokon Stanislav(EPAM)[GCP]https://community.opengroup.org/osdu/platform/system/lib/cloud/gcp/osm/-/merge_requests/48Cherry-pick 'Upgrade First Party Library Dependencies for Release 0.21' into ...2023-05-23T15:16:35ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Upgrade First Party Library Dependencies for Release 0.21' into release/0.21**Original MR**: !45
### 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 incorporatin...**Original MR**: !45
### 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/cloud/gcp/osm/-/pipelines/new?ref=cherry-pick-for-45)M18 - Release 0.21David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/lib/cloud/gcp/osm/-/merge_requests/47Cherry-pick 'GONRG-7029, Updating anthos to baremetal' into release/0.212023-05-23T15:15:02ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'GONRG-7029, Updating anthos to baremetal' into release/0.21**Original MR**: !46
### 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 incorporatin...**Original MR**: !46
### 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/cloud/gcp/osm/-/pipelines/new?ref=cherry-pick-for-46)M18 - Release 0.21David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/lib/cloud/gcp/osm/-/merge_requests/46GONRG-7029, Updating anthos to baremetal2023-05-23T15:13:22ZDavid Diederichd.diederich@opengroup.orgGONRG-7029, Updating anthos to baremetalFollowing in the footsteps of [several other MRs](https://community.opengroup.org/groups/osdu/-/merge_requests?scope=all&state=merged&search=GONRG-7029) to this effectFollowing in the footsteps of [several other MRs](https://community.opengroup.org/groups/osdu/-/merge_requests?scope=all&state=merged&search=GONRG-7029) to this effectM18 - Release 0.21https://community.opengroup.org/osdu/platform/system/lib/cloud/gcp/osm/-/merge_requests/45Upgrade First Party Library Dependencies for Release 0.212023-05-23T15:15:30ZDavid Diederichd.diederich@opengroup.orgUpgrade First Party Library Dependencies for Release 0.21This 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: main
SHA: ef39c7c0436a063fcfc81c8601a95ee5bb1e6b0e
Maven: 0.21.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------ | ---------- | ---------- |
| os-core-common | 0.21.0-rc3 | 0.21.0-rc3 |
### Dependency Information After the Upgrade
```
Branch: dependency-upgrade
SHA: 48ca4cb80eac05f894dcdb4afaf0426a058570ae
Maven: 0.21.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------ | ------ | -------- |
| os-core-common | 0.21.0 | 0.21.0 |M18 - Release 0.21Rustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comRiabokon Stanislav(EPAM)[GCP]Andrei Dalhikh [EPAM/GC]Rustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comhttps://community.opengroup.org/osdu/platform/system/lib/cloud/gcp/osm/-/merge_requests/44Cherry-pick 'Upgrading SnakeYAML and Spring Boot to address CVE-2022-1471' in...2023-04-07T14:36:38ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Upgrading SnakeYAML and Spring Boot to address CVE-2022-1471' into release/0.20**Original MR**: !43
### 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 incorporatin...**Original MR**: !43
### 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/cloud/gcp/osm/-/pipelines/new?ref=cherry-pick-for-43)M17 - Release 0.20David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/lib/cloud/gcp/osm/-/merge_requests/43Upgrading SnakeYAML and Spring Boot to address CVE-2022-14712023-04-07T13:36:05ZDavid Diederichd.diederich@opengroup.orgUpgrading SnakeYAML and Spring Boot to address CVE-2022-1471This upgrades the SnakeYAML dependency to be version 2.0, addressing a critical security vulnerability ([CVE-2022-1471](https://nvd.nist.gov/vuln/detail/CVE-2022-1471)).
It required explicitly setting the dependency rather than allowing...This upgrades the SnakeYAML dependency to be version 2.0, addressing a critical security vulnerability ([CVE-2022-1471](https://nvd.nist.gov/vuln/detail/CVE-2022-1471)).
It required explicitly setting the dependency rather than allowing it to be inherited from Spring Boot.
Furthermore, Spring Boot 2.7.2 wasn't compatible with the SnakeYAML upgrade, so I upgraded that to 2.7.10 to pass the tests.
Closes #3M17 - Release 0.20David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/lib/cloud/gcp/osm/-/merge_requests/42Added transaction error message (GONRG-6800)2023-03-28T11:41:19ZYurii Ruban [EPAM / GCP]Added transaction error message (GONRG-6800)# Description:
Added describing error for the datastore transaction.
# How to test:
Check the message in the register service (or other services) with an error conflict in the datastore transaction.
# Changes include:
- [x] Refactor...# Description:
Added describing error for the datastore transaction.
# How to test:
Check the message in the register service (or other services) with an error conflict in the datastore transaction.
# Changes include:
- [x] Refactor (a non-breaking change that improves code maintainability).
# Changes in:
- [x] GCPM17 - Release 0.20Riabokon Stanislav(EPAM)[GCP]Riabokon Stanislav(EPAM)[GCP]https://community.opengroup.org/osdu/platform/system/lib/cloud/gcp/osm/-/merge_requests/41added IN operator, tests, lib upgrade2023-04-05T12:04:54ZRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comadded IN operator, tests, lib upgrade# Description:
- Added `IN` filter to OSM
- Implement it for Datastore and Postgres
- Added Int tests for the new filter
- Untie the Context class from the redundant inheritance of the QueryRunner interface
# Changes include:
- [ ] R...# Description:
- Added `IN` filter to OSM
- Implement it for Datastore and Postgres
- Added Int tests for the new filter
- Untie the Context class from the redundant inheritance of the QueryRunner interface
# 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] Datastore
- [x] Postgres
- [x] Common code
# Dev Checklist:
- [x] Added Unit Tests, wherever applicable.
- [ ] 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:
- Datastore `IN` filter is limited with 30 parameters inside 1 filter, we had to split such queries.
- For the intersection of `IN` filters in Datastore even more excessive workarounds are required, 2 filters with (30+N) values produce 2x(30+N) separate queries to define intersection later in memory. Because of that such cases were moved under the feature flag and disabled by default. If the necessity appears we may rework it(currently there is no such in related services).M18 - Release 0.21Rustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.com