CRS Catalog merge requestshttps://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests2023-10-12T18:47:29Zhttps://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/318fix plexus version2023-10-12T18:47:29ZNathan Strelserfix plexus versionhttps://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/317[GONRG-7917] added replicas variable in helm2023-10-12T13:13:50ZAleksandr Primachenko [EPAMĀ / GCP][GONRG-7917] added replicas variable in helmM21 - Release 0.24https://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/316mege to gitlab2023-10-12T16:11:00ZYunhua Koglinmege to gitlabM21 - Release 0.24Yunhua KoglinYunhua Koglinhttps://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/315[GONRG-7834] added livenessProbe2023-10-11T13:41:17ZAleksandr Primachenko [EPAMĀ / GCP][GONRG-7834] added livenessProbeM21 - Release 0.24https://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/314fix jackson-databind-vulnerability2023-10-09T06:18:28ZVidyaDharani Lokamfix jackson-databind-vulnerability# Change details
* upgrade `jackson-databind` to `2.15.2`
# Changes in:
* [x] GCP
* [ ] Azure
* [x] AWS
* [x] IBM# Change details
* upgrade `jackson-databind` to `2.15.2`
# Changes in:
* [x] GCP
* [ ] Azure
* [x] AWS
* [x] IBMM21 - Release 0.24VidyaDharani LokamVidyaDharani Lokamhttps://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/313fix azure jackson-databind vulnerability2023-10-09T06:18:29ZVidyaDharani Lokamfix azure jackson-databind vulnerability# Change details
* upgrade `jackson-databind` to `2.15.2`
# Changes in:
* [ ] GCP
* [x] Azure
* [ ] AWS
* [ ] IBM# Change details
* upgrade `jackson-databind` to `2.15.2`
# Changes in:
* [ ] GCP
* [x] Azure
* [ ] AWS
* [ ] IBMM21 - Release 0.24VidyaDharani LokamVidyaDharani Lokamhttps://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/312Remediate guava dependency vulnerability and cleanup 'documentdb-bulkexecutor'2023-10-03T06:51:18ZThulasi Dass SubramanianRemediate guava dependency vulnerability and cleanup 'documentdb-bulkexecutor'# Change details
* excluded unused dependency `documentdb-bulkexecutor` to remove `guava:24.1.1-jre` version with vulnerabilities
* upgrade `io.netty:netty-bom` version to `4.1.98.Final`
# Changes in:
* [ ] GCP
* [x] Azure
* [ ] AWS
*...# Change details
* excluded unused dependency `documentdb-bulkexecutor` to remove `guava:24.1.1-jre` version with vulnerabilities
* upgrade `io.netty:netty-bom` version to `4.1.98.Final`
# Changes in:
* [ ] GCP
* [x] Azure
* [ ] AWS
* [ ] IBMM21 - Release 0.24Thulasi Dass SubramanianThulasi Dass Subramanianhttps://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/311include json-smart dependency2023-09-21T23:09:46ZNathan Strelserinclude json-smart dependencyNathan StrelserNathan Strelserhttps://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/309Introduce variable for java Integration test2023-09-15T13:58:59Zsaketh somarajuIntroduce variable for java Integration test* This MR introduces a variable to manage java integration test in azure ci-cd pipeline
* This change would help in configuring azure integration test seamlessly* This MR introduces a variable to manage java integration test in azure ci-cd pipeline
* This change would help in configuring azure integration test seamlesslyM21 - Release 0.24saketh somarajusaketh somarajuhttps://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/308Remediate netty-handler vulnerability in Azure2023-09-13T06:41:28ZThulasi Dass SubramanianRemediate netty-handler vulnerability in Azure# Change details
* upgrade `io.netty:netty-bom` version to `4.1.96.Final`
# Changes in:
* [ ] GCP
* [x] Azure
* [ ] AWS
* [ ] IBM# Change details
* upgrade `io.netty:netty-bom` version to `4.1.96.Final`
# Changes in:
* [ ] GCP
* [x] Azure
* [ ] AWS
* [ ] IBMM21 - Release 0.24Thulasi Dass SubramanianThulasi Dass Subramanianhttps://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/307Cherry-pick 'Upgrade First Party Library Dependencies for Release 0.23' into ...2023-09-05T21:05:58ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Upgrade First Party Library Dependencies for Release 0.23' into release/0.23**Original MR**: !306
### 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**: !306
### 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/reference/crs-catalog-service/-/pipelines/new?ref=cherry-pick-for-306)M20 - Release 0.23David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/306Upgrade First Party Library Dependencies for Release 0.232023-09-05T21:05:37ZDavid 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: master
SHA: ee3968c9049003bfbf1f681471abc51f66b22885
Maven: 0.24.0-SNAPSHOT
```
| Maven Dependencies | _Root_ |
| ------------------ | ------ |
| core-lib-azure | 0.22.0 |
| os-core-common | 0.23.1 |
| os-core-lib-ibm | 0.23.0 |
### Dependency Information After the Upgrade
```
Branch: dependency-upgrade
SHA: 71e22f4f997c66d0c1182c23965fb6b4a9c2aadd
Maven: 0.24.0-SNAPSHOT
```
| Maven Dependencies | _Root_ |
| ------------------ | ------ |
| core-lib-azure | 0.23.1 |
| os-core-common | 0.23.2 |
| os-core-lib-ibm | 0.23.0 |M20 - Release 0.23https://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/305Cherry-pick 'Upgrade First Party Library Dependencies for Release 0.23' into ...2023-09-04T18:21:24ZChad LeongCherry-pick 'Upgrade First Party Library Dependencies for Release 0.23' into release/0.23**Original MR**: !304
### 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**: !304
### 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/reference/crs-catalog-service/-/pipelines/new?ref=cherry-pick-for-304)M20 - Release 0.23David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/304Upgrade First Party Library Dependencies for Release 0.232023-09-04T17:44:30ZDavid 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: master
SHA: 5a38b454f41133c322ba54fa801ba38491f9baee
Maven: 0.24.0-SNAPSHOT
```
| Maven Dependencies | _Root_ |
| ------------------ | ------ |
| core-lib-azure | 0.22.0 |
| os-core-common | 0.22.0 |
| os-core-lib-ibm | 0.22.0 |
### Dependency Information After the Upgrade
```
Branch: dependency-upgrade
SHA: 3e4b7faea9987030822d54ce38f500faaee1944e
Maven: 0.24.0-SNAPSHOT
```
| Maven Dependencies | _Root_ |
| ------------------ | ------ |
| core-lib-azure | 0.22.0 |
| os-core-common | 0.23.1 |
| os-core-lib-ibm | 0.23.0 |M20 - Release 0.23https://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/303AWS sync dev to master2023-08-19T17:03:07ZLong ChengAWS sync dev to masterAWS sync dev to masterAWS sync dev to masterM20 - Release 0.23Long ChengLong Chenghttps://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/301trusted-delta-changes-from-m162023-08-21T21:09:57ZVaibhavi Kamanitrusted-delta-changes-from-m16trusted-delta-changes-from-m16trusted-delta-changes-from-m16Vaibhavi KamaniVaibhavi Kamanihttps://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/300fixing vulnerabilities.2023-09-06T19:32:46ZHarsheet Shahfixing vulnerabilities.Fixing vulnerabilities by upgrading libraries.Fixing vulnerabilities by upgrading libraries.Harsheet ShahHarsheet Shahhttps://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/299added exclusion to security filter for apidocs endpoint(GONRG-7592)2023-08-09T13:36:21ZRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comadded exclusion to security filter for apidocs endpoint(GONRG-7592)Issue: https://community.opengroup.org/osdu/platform/pre-shipping/-/issues/560Issue: https://community.opengroup.org/osdu/platform/pre-shipping/-/issues/560M20 - Release 0.23Rustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comhttps://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/298Optimized Swagger UI API Versions Order to Encourage Adoption of Latest APIs2023-08-09T05:18:48ZJayesh BagulOptimized Swagger UI API Versions Order to Encourage Adoption of Latest APIsIn this merge request, Rearranged API version order in the Swagger UI dropdown. By placing the latest version at the forefront encouraging users to explore and adopt most up-to-date APIs.In this merge request, Rearranged API version order in the Swagger UI dropdown. By placing the latest version at the forefront encouraging users to explore and adopt most up-to-date APIs.M20 - Release 0.23Jayesh BagulJayesh Bagulhttps://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/297Resolve "Update CRS Catalog tutorial"2023-09-11T15:41:00ZBert KampesResolve "Update CRS Catalog tutorial"Closes #33Closes #33M21 - Release 0.24Bert KampesBert Kampes