Partition merge requestshttps://community.opengroup.org/osdu/platform/system/partition/-/merge_requests2023-06-19T11:20:20Zhttps://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/407GONRG-6991: add variables for Reservoir2023-06-19T11:20:20ZYauheni Rykhter (EPAM)GONRG-6991: add variables for ReservoirM19 - Release 0.22Yauheni Rykhter (EPAM)Yauheni Rykhter (EPAM)https://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/406vulnerability fix2023-06-19T07:31:07ZKamalika Sahavulnerability fixKamalika SahaKamalika Sahahttps://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/405Cherry-pick 'Adding versions to the provider POMs' into release/0.212023-06-07T10:12:27ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Adding versions to the provider POMs' into release/0.21**Original MR**: !404
### 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**: !404
### 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/partition/-/pipelines/new?ref=cherry-pick-for-404)M18 - Release 0.21David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/404Adding versions to the provider POMs2023-06-07T10:11:41ZDavid Diederichd.diederich@opengroup.orgAdding versions to the provider POMsThis is necessary to create a provider specific release. When creating a provider specific release, the artifact version of the single provider is incremented, then a special tag is created to indicate the change only refers to that one ...This is necessary to create a provider specific release. When creating a provider specific release, the artifact version of the single provider is incremented, then a special tag is created to indicate the change only refers to that one provider.
In the existing case, there are no versions specified for provider libraries. That causes maven to inherit the version from the parent, which in turn forces all provider libraries to have the same version. We need to explicitly set the versions in order to have different ones per provider.M18 - Release 0.21David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/403Upgraded mappers (GONRG-7015)2023-06-05T13:14:48ZRiabokon Stanislav(EPAM)[GCP]Upgraded mappers (GONRG-7015)Upgraded mappersUpgraded mappersM19 - Release 0.22Riabokon Stanislav(EPAM)[GCP]Riabokon Stanislav(EPAM)[GCP]https://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/402Merge branch 'gc-fix-context' into 'master'2023-06-05T09:17:13ZRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comMerge branch 'gc-fix-context' into 'master'Fix spring context for GC baremetal
See merge request osdu/platform/system/partition!401
(cherry picked from commit 01d870e86ea3fc7f966295fb74cd8494fb8c3c87)
ed3ba6d4 exclude partition based config beanFix spring context for GC baremetal
See merge request osdu/platform/system/partition!401
(cherry picked from commit 01d870e86ea3fc7f966295fb74cd8494fb8c3c87)
ed3ba6d4 exclude partition based config beanM18 - Release 0.21Rustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comhttps://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/401Fix spring context for GC baremetal2023-06-08T04:12:44ZRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comFix spring context for GC baremetalM18 - Release 0.21Rustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comhttps://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/400changed kube sa name2023-07-28T13:04:08ZOrest Khud [EPAM / GCP]changed kube sa nameM20 - Release 0.23https://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/399Cherry-pick 'Upgrade First Party Library Dependencies for Release 0.21' into ...2023-05-31T20:27:20ZChad LeongCherry-pick 'Upgrade First Party Library Dependencies for Release 0.21' into release/0.21**Original MR**: !397
### 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**: !397
### 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/partition/-/pipelines/new?ref=cherry-pick-for-397)M18 - Release 0.21David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/398Draft: dummy mr2023-12-08T15:20:25Zshivani karipeDraft: dummy mrhttps://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/397Upgrade First Party Library Dependencies for Release 0.212023-05-31T19:35:14ZDavid 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: master
SHA: 787d85537fb61f0d80ab36a49a24aa92783f5301
Maven: 0.22.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| --------------------------------------------------- | --------------- | -------------- |
| core-lib-azure | 0.20.0 | |
| core-lib-gc | 0.21.0-rc3 | 0.20.0 |
| os-core-lib-aws | 0.21.0-rc5 | 0.21.0-rc5 |
| obm | 0.20.0 | 0.20.0 |
| oqm | 0.20.0 | 0.20.0 |
| os-core-common | 0.20.1 | 0.20.1 |
| os-core-lib-ibm | 0.20.0 | 0.20.0 |
| osm | 0.21.0-rc2 | 0.20.0 |
| (3rd Party) org.apache.logging.log4j.log4j-api | 2.17.1, 2.17.2 | 2.17.2, 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-to-slf4j | 2.17.1, 2.17.2 | 2.17.2, 2.13.3 |
| (3rd Party) org.yaml.snakeyaml | 2.0, 1.33, 1.30 | 1.30, 2.0 |
```
Critical: Found Vulnerable Snake YAML dependency (<2.0)
├─ _Root_
│ ├─ org.opengroup.osdu.partition-ibm == 0.22.0-SNAPSHOT
│ │ └─ org.yaml.snakeyaml == 1.33
│ └─ org.opengroup.osdu.partition-gc == 0.22.0-SNAPSHOT
│ └─ org.springframework.boot.spring-boot-starter-security == 2.7.10
│ └─ org.springframework.boot.spring-boot-starter == 2.7.10
│ └─ org.yaml.snakeyaml == 1.30
└─ testing/
├─ org.opengroup.osdu.partition.partition-test-aws == 0.22.0-SNAPSHOT
│ └─ org.opengroup.osdu.core.aws.os-core-lib-aws == 0.21.0-rc5
│ └─ org.springframework.boot.spring-boot-starter-web == 2.7.7
│ └─ org.springframework.boot.spring-boot-starter == 2.7.7
│ └─ org.yaml.snakeyaml == 1.30
└─ org.opengroup.osdu.partition.partition-test-gc == 0.22.0-SNAPSHOT
└─ org.opengroup.osdu.core-lib-gc == 0.20.0
└─ org.opengroup.osdu.oqm == 0.20.0
└─ org.springframework.boot.spring-boot-starter == 2.7.10
└─ org.yaml.snakeyaml == 1.30
```
### Dependency Information After the Upgrade
```
Branch: dependency-upgrade
SHA: a6d69a7c5f356e0dc290833497804844d8008cd3
Maven: 0.22.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| --------------------------------------------------- | --------------- | -------------- |
| core-lib-azure | 0.21.0 | |
| core-lib-gc | 0.21.0 | 0.21.0 |
| os-core-lib-aws | 0.21.0 | 0.21.0 |
| os-core-common | 0.21.0 | 0.21.0 |
| os-core-lib-ibm | 0.21.0 | 0.21.0 |
| (3rd Party) org.apache.logging.log4j.log4j-api | 2.17.1, 2.17.2 | 2.17.2, 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-to-slf4j | 2.17.1, 2.17.2 | 2.17.2, 2.13.3 |
| (3rd Party) org.yaml.snakeyaml | 2.0, 1.33, 1.30 | 1.30, 2.0 |
```
Critical: Found Vulnerable Snake YAML dependency (<2.0)
├─ _Root_
│ ├─ org.opengroup.osdu.partition-ibm == 0.22.0-SNAPSHOT
│ │ └─ org.yaml.snakeyaml == 1.33
│ └─ org.opengroup.osdu.partition-gc == 0.22.0-SNAPSHOT
│ └─ org.springframework.boot.spring-boot-starter-security == 2.7.10
│ └─ org.springframework.boot.spring-boot-starter == 2.7.10
│ └─ org.yaml.snakeyaml == 1.30
└─ testing/
├─ org.opengroup.osdu.partition.partition-test-aws == 0.22.0-SNAPSHOT
│ └─ org.opengroup.osdu.core.aws.os-core-lib-aws == 0.21.0
│ └─ org.springframework.boot.spring-boot-starter-web == 2.7.7
│ └─ org.springframework.boot.spring-boot-starter == 2.7.7
│ └─ org.yaml.snakeyaml == 1.30
└─ org.opengroup.osdu.partition.partition-test-gc == 0.22.0-SNAPSHOT
└─ org.opengroup.osdu.core-lib-gc == 0.21.0
└─ org.opengroup.osdu.os-core-common == 0.21.0
└─ org.springframework.boot.spring-boot-starter-web == 2.7.7
└─ org.springframework.boot.spring-boot-starter == 2.7.7
└─ org.yaml.snakeyaml == 1.30
```M18 - Release 0.21https://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/396Indexer augmenter property2023-05-25T11:51:37ZRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comIndexer augmenter propertyRelates to https://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/465 and https://community.opengroup.org/osdu/platform/system/indexer-service/-/issues/81Relates to https://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/465 and https://community.opengroup.org/osdu/platform/system/indexer-service/-/issues/81M19 - Release 0.22Rustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comYauheni Rykhter (EPAM)Rustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comhttps://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/395Draft: dummy2023-12-08T15:20:25Zshivani karipeDraft: dummyhttps://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/394Fixing variable for aws2023-05-19T21:55:29ZAbhay JoshiFixing variable for aws(cherry picked from commit ace3bd26f255cd6e82c012e6f06bf991ae0de13d)(cherry picked from commit ace3bd26f255cd6e82c012e6f06bf991ae0de13d)M18 - Release 0.21Abhay JoshiYong ZengMadalyn MarabellaAbhay Joshihttps://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/393Update images for OpenJDK2023-05-19T14:04:23ZOrest Khud [EPAM / GCP]Update images for OpenJDKM18 - Release 0.21https://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/392upgrade maven dependency version2023-05-19T15:55:13Zsaketh somarajuupgrade maven dependency version[Partition vulnerability 3329](https://community.opengroup.org/osdu/platform/system/partition/-/security/vulnerabilities/3329)
[issue 127](https://community.opengroup.org/osdu/platform/security-and-compliance/home/-/issues/127)[Partition vulnerability 3329](https://community.opengroup.org/osdu/platform/system/partition/-/security/vulnerabilities/3329)
[issue 127](https://community.opengroup.org/osdu/platform/security-and-compliance/home/-/issues/127)M18 - Release 0.21saketh somarajusaketh somarajuhttps://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/391adding useragent changes2023-05-12T16:40:54ZAbhay Joshiadding useragent changes(cherry picked from commit 9001a98e78aa080ec23fe4eeac59a510e9256f44)(cherry picked from commit 9001a98e78aa080ec23fe4eeac59a510e9256f44)M18 - Release 0.21Okoun-Ola Fabien HouetoAbhay JoshiYong ZengOkoun-Ola Fabien Houetohttps://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/390M14DeltaChanges to M162023-05-11T22:15:56ZOsborn ChenM14DeltaChanges to M16Fix CG vulnerabilities for Partition
See merge request osdu/platform/system/partition!385Fix CG vulnerabilities for Partition
See merge request osdu/platform/system/partition!385Osborn ChenOsborn Chenhttps://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/389base image changed2023-05-12T14:42:42ZOrest Khud [EPAM / GCP]base image changedM18 - Release 0.21https://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/388update NOTICE file2023-05-11T15:15:14ZMadalyn Marabellaupdate NOTICE fileM18 - Release 0.21Madalyn MarabellaMadalyn Marabella