CRS Catalog merge requestshttps://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests2023-01-09T16:18:44Zhttps://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/232fixing dependency check2023-01-09T16:18:44ZMarc Burnie [AWS]fixing dependency checkM16 - Release 0.19Marc Burnie [AWS]Marc Burnie [AWS]https://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/231temporarily bypass maven dependency check2023-01-07T03:06:16ZMorris Estepatemporarily bypass maven dependency checkM16 - Release 0.19Morris EstepaMorris Estepahttps://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/228Fix spring-boot-starter vulnerability2023-01-03T11:40:12ZThulasi Dass SubramanianFix spring-boot-starter vulnerability* fixed spring-boot-starter web & webflux vulnerabilities* fixed spring-boot-starter web & webflux vulnerabilitiesM16 - Release 0.19Thulasi Dass SubramanianThulasi Dass Subramanianhttps://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/226Updated core lib for cors2023-01-03T05:46:04ZVineeth Guna [Microsoft]Updated core lib for corshttps://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/227[GONRG-6178] Decrease ISTIO requests and limits2023-01-12T23:53:22ZOleksandr Kosse (EPAM)[GONRG-6178] Decrease ISTIO requests and limitsDecrease ISTIO requests and limits for crs-catalog serviceDecrease ISTIO requests and limits for crs-catalog serviceM16 - Release 0.19https://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/224Upgrade spring-boot-maven-plugin to 2.7.62022-12-13T13:51:07ZNaveen RamachandraiahUpgrade spring-boot-maven-plugin to 2.7.6Naveen RamachandraiahNaveen Ramachandraiahhttps://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/223Cherry-pick 'jar type vulnerability fix for catalog service' into release/0.182022-12-12T16:45:54ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'jar type vulnerability fix for catalog service' into release/0.18**Original MR**: !220
### 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**: !220
### 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-220)M15 - Release 0.18David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/220jar type vulnerability fix for catalog service2022-12-12T15:52:01ZPintu Guptajar type vulnerability fix for catalog serviceM15 - Release 0.18Pintu GuptaPintu Guptahttps://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/218GONRG-5952: Merge GC helms to the common one2023-08-18T13:52:11ZVolodymyr Pienskoi [EPAM / GCP]GONRG-5952: Merge GC helms to the common oneM16 - Release 0.19Volodymyr Pienskoi [EPAM / GCP]Volodymyr Pienskoi [EPAM / GCP]https://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/222Update FOSSA NOTICE2022-12-11T05:11:08ZDavid 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.M16 - Release 0.19https://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/219Fixed vulnerabilities2022-12-09T11:53:42ZVineeth Guna [Microsoft]Fixed vulnerabilitieshttps://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/217Cherry-pick 'added changes to disable the azure code coverage' into release/0.182023-02-03T21:57:42ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'added changes to disable the azure code coverage' into release/0.18**Original MR**: !213
### 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**: !213
### 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-213)M15 - Release 0.18David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/213added changes to disable the azure code coverage2022-12-06T12:40:44Zshivani karipeadded changes to disable the azure code coverageM15 - Release 0.18shivani karipeshivani karipehttps://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/215Merge AWS changes to master2022-12-02T21:20:45ZMorris EstepaMerge AWS changes to mastercommit 4faf01a8
Author: Abhay <bios@amazon.com>
Date: Wed Nov 30 2022 08:14:33 GMT-0800 (Pacific Standard Time)
downgrade spring-boot-maven-plugincommit 4faf01a8
Author: Abhay <bios@amazon.com>
Date: Wed Nov 30 2022 08:14:33 GMT-0800 (Pacific Standard Time)
downgrade spring-boot-maven-pluginM15 - Release 0.18Morris EstepaMorris Estepahttps://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/206Duplicate ibm CICD file removed2022-11-29T10:57:06ZAshwani PandeyDuplicate ibm CICD file removedRemoving Duplicate CICD fileRemoving Duplicate CICD fileM15 - Release 0.18Ashwani PandeyAshwani Pandeyhttps://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/205M14 Upgrade2022-11-23T11:27:56ZAnkur RawatM14 UpgradeM12 changes into M14M12 changes into M14Ankur RawatAnkur Rawathttps://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/203Merge latest AWS fixes, version updates2022-11-18T23:42:05ZMorris EstepaMerge latest AWS fixes, version updatescommit 24132ac2
Author: David Meng <xlmeng@amazon.com>
Date: Mon Sep 26 2022 16:08:13 GMT-0400 (Eastern Daylight Time)
Upgrade Gsoncommit 24132ac2
Author: David Meng <xlmeng@amazon.com>
Date: Mon Sep 26 2022 16:08:13 GMT-0400 (Eastern Daylight Time)
Upgrade GsonM15 - Release 0.18Morris EstepaMorris Estepahttps://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/202Cherry-pick 'Merge ibm helm' into release/0.172022-10-10T18:08:52ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Merge ibm helm' into release/0.17**Original MR**: !201
### 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**: !201
### 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-201)M14 - Release 0.17David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/201Merge ibm helm2022-10-10T05:59:28ZManish SinghMerge ibm helmMerge ibm helm to masterMerge ibm helm to masterM14 - Release 0.17Anuj GuptaAnuj Guptahttps://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/196Initial skeleton to be edited2023-08-18T13:52:12ZBert KampesInitial skeleton to be editedhow to tutorial for CRS Cataloghow to tutorial for CRS CatalogM15 - Release 0.18Bert KampesBert Kampes