Notification merge requestshttps://community.opengroup.org/osdu/platform/system/notification/-/merge_requests2024-03-21T15:01:34Zhttps://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/494Documentation update with mkdocs2024-03-21T15:01:34ZChad LeongDocumentation update with mkdocs* Documentation update
* Publish to [pages](https://osdu.pages.opengroup.org/platform/system/notification/)* Documentation update
* Publish to [pages](https://osdu.pages.opengroup.org/platform/system/notification/)M23 - Release 0.26Shane HutchinsShane Hutchinshttps://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/493Fix Azure spring 6 upgrade2024-03-19T06:16:36ZThulasi Dass SubramanianFix Azure spring 6 upgrade* upgraded Azure related dependencies for \[Spring boot 3, Spring 6\] compatibility
* Azure only changes* upgraded Azure related dependencies for \[Spring boot 3, Spring 6\] compatibility
* Azure only changesM23 - Release 0.26Thulasi Dass SubramanianThulasi Dass Subramanianhttps://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/492[GONRG-9422]: Remove springProfilesActive explicit setting2024-03-20T12:38:57ZMykola Ronik [EPAM / GCP][GONRG-9422]: Remove springProfilesActive explicit setting## Type of change
- [ ] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
https://jiraeu.epam.com/browse/GONRG-9422
## Does this introduce a change in the core logic?
- [NO]
## Does...## Type of change
- [ ] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
https://jiraeu.epam.com/browse/GONRG-9422
## 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
- [x] Google Cloud
- [ ] IBM
## Does this introduce a breaking change?
- [NO]M23 - Release 0.26Mykola Ronik [EPAM / GCP]Mykola Ronik [EPAM / GCP]https://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/491Upgrade service to spring 6 and Spring-boot 32024-03-27T16:37:57ZSolomon AyalewUpgrade service to spring 6 and Spring-boot 3Upgrade service to spring 6 and Spring-boot 3Upgrade service to spring 6 and Spring-boot 3M23 - Release 0.26https://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/488Removing message from Service Bus after 10 retries2024-03-21T13:30:33ZKamalika SahaRemoving message from Service Bus after 10 retries## Type of change
- [ ] Bug Fix
- [ ] Feature
code change for avoiding the message to go into dead letter queue after 10 retries.
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a...## Type of change
- [ ] Bug Fix
- [ ] Feature
code change for avoiding the message to go into dead letter queue after 10 retries.
**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?
- [ ] AWS
- [x] Azure
- [ ] Google Cloud
- [ ] IBM
## Does this introduce a breaking change?
- [NO]
## What is the current behavior?
Message goes into Dead letter queue after 10 retries.
## What is the new/expected behavior?
Message should get deleted from Service Bus instead of going into dead letter queue.
## Have you added/updated Unit Tests and Integration Tests?
Exception Message : " Max Delivery Count of 5 Exceeded for Message with id : d3080107-bd34-4d85-a2f1-9fb32c3e3452-0-62d81cd8-8902-4d96-9416-2df1257a0916 for Subscription : de-4c25167b-d295-4438-b2f7-42946f4eb33b; Completing the message java.lang.Exception: message not acknowledged by client| "
Normal Service IT run without my changes : [Pipelines - Run 20240304.4](https://openenergyplatform.visualstudio.com/Open%20Energy%20Platform/_build/results?buildId=168743&view=results)
Service IT run with my changes : [Pipelines - Run 20240304.5](https://openenergyplatform.visualstudio.com/Open%20Energy%20Platform/_build/results?buildId=168808&view=results)
(Notification Image Pushed into the instance)
## Any other useful informationM23 - Release 0.26Kamalika SahaKamalika Sahahttps://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/486[#MSCOSDU-36100] upgrade : core-lib-azure Java 17 version2024-03-08T06:33:58ZThulasi Dass Subramanian[#MSCOSDU-36100] upgrade : core-lib-azure Java 17 version## Change details
* For Azure only: upgraded `core-lib-azure` version to `0.26.0-rc5` for Java 17 updates both in source & testing modules
## Changes in:
* [ ] GCP
* [x] Azure
* [ ] AWS
* [ ] IBM## Change details
* For Azure only: upgraded `core-lib-azure` version to `0.26.0-rc5` for Java 17 updates both in source & testing modules
## Changes in:
* [ ] GCP
* [x] Azure
* [ ] AWS
* [ ] IBMM23 - Release 0.26Thulasi Dass SubramanianThulasi Dass Subramanianhttps://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/485[GONRG-9211] Added labels to gc helm2024-03-19T17:11:40ZDanylo Vanin (EPAM)[GONRG-9211] Added labels to gc helmM23 - Release 0.26Danylo Vanin (EPAM)Danylo Vanin (EPAM)https://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/484Address sonar warnings2024-03-04T18:05:23ZSolomon AyalewAddress sonar warningsM23 - Release 0.26https://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/483Update lib2024-03-19T17:11:42ZRucha 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/notification/-/merge_requests/482Fix local build testing2024-02-12T21:27:23ZDerek HudsonFix local build testing## 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?
Build does not pass on AWS build.
## What is the new/expected behavior?
Build should pass on AWS build.
## Have you added/updated Unit Tests and Integration Tests?
## Any other useful informationM23 - Release 0.26Derek HudsonDerek Hudsonhttps://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/481[MSCOSDU-2120] fix spring-security-core vulnerability2024-02-02T16:24:33ZVidyaDharani Lokam[MSCOSDU-2120] fix spring-security-core vulnerability# Change details
* issue reference: https://community.opengroup.org/osdu/platform/system/notification/-/issues/80
* updated `spring-security-core` dependency to `5.7.11` remediate vulnerability.
# Changes in:
* [ ] Azure
* [x] AWS
* [...# Change details
* issue reference: https://community.opengroup.org/osdu/platform/system/notification/-/issues/80
* updated `spring-security-core` dependency to `5.7.11` remediate vulnerability.
# Changes in:
* [ ] Azure
* [x] AWS
* [ ] GCP
* [ ] IBMM23 - Release 0.26VidyaDharani LokamVidyaDharani Lokamhttps://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/480Solxget/fork2024-01-24T23:43:33ZSolomon AyalewSolxget/forkhttps://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/479Fix vulnerabilities2024-01-25T18:29:39ZSolomon AyalewFix vulnerabilitiesaddress the following vulnerabilties except spring-core.
| CVE-2022-22965 | CRITICAL | org.springframework:spring-beans-5.3.13 | Java | os_notification |
|------------------|----------|------------------------------------------|----...address the following vulnerabilties except spring-core.
| CVE-2022-22965 | CRITICAL | org.springframework:spring-beans-5.3.13 | Java | os_notification |
|------------------|----------|------------------------------------------|------|-----------------|
| CVE-2022-22968 | HIGH | org.springframework:spring-core-5.3.13 | Java | os_notification |
| CVE-2022-22970 | HIGH | org.springframework:spring-core-5.3.13 | Java | os_notification |
| CVE-2023-20863 | HIGH | org.springframework:spring-core-5.3.13 | Java | os_notification |
| CVE-2022-22965 | CRITICAL | org.springframework:spring-webmvc-5.3.13 | Java | os_notification |
| CVE-2022-1471 | HIGH | org.yaml:snakeyaml-1.30 | Java | os_notification |
| CVE-2022-25857 | HIGH | org.yaml:snakeyaml-1.30 | Java | os_notification |M23 - Release 0.26https://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/478test fix2024-01-25T05:41:00ZNikhil Patilnikhil.patil5@ibm.comtest fixM23 - Release 0.26Nikhil Patilnikhil.patil5@ibm.comNikhil Patilnikhil.patil5@ibm.comhttps://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/477Cherry-pick 'Notification updated ibm lib version' into release/0.252024-01-09T12:05:01ZChad LeongCherry-pick 'Notification updated ibm lib version' into release/0.25**Original MR**: !475
### 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**: !475
### 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/notification/-/pipelines/new?ref=cherry-pick-for-475)M22 - Release 0.25David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/476[MSCOSDU-1894] upgrade json-smart and reactor-netty2024-01-05T11:58:55ZVidyaDharani Lokam[MSCOSDU-1894] upgrade json-smart and reactor-netty* upgraded `json-smart` to `2.5.0` to remediate vulnerability.
* upgraded `reactor-netty` to `1.1.14`.
* upgraded `core-lib-azure` to `0.25.0`.* upgraded `json-smart` to `2.5.0` to remediate vulnerability.
* upgraded `reactor-netty` to `1.1.14`.
* upgraded `core-lib-azure` to `0.25.0`.M23 - Release 0.26VidyaDharani LokamVidyaDharani Lokamhttps://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/475Notification updated ibm lib version2024-01-09T11:43:43ZIsha KumariNotification updated ibm lib versionNotification updated ibm lib versionNotification updated ibm lib versionM22 - Release 0.25Isha KumariIsha Kumarihttps://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/472Use full URL instead of relative path2024-02-06T09:39:44ZLawrence ChanUse full URL instead of relative path* Issue Reference: [#68](https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/issues/68)
* Added configuration `api.server.fullUrl.enabled` to enable full server url in OpenAPI swagger
* Currently only in Azure i...* Issue Reference: [#68](https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/issues/68)
* Added configuration `api.server.fullUrl.enabled` to enable full server url in OpenAPI swagger
* Currently only in Azure it is enabled. For Other \[CSP/Common Core\] there is no change.
### Configuration Details
* `api.server.fullUrl.enabled=true` It will generate full server url in the OpenAPI swagger
* `api.server.fullUrl.enabled=false` It will generate only the contextPath
* Reference: https://springdoc.org/faq.html#_how_is_server_url_generatedM23 - Release 0.26https://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/471Cherry-pick: Merge branch 'gc-fix-cache' into 'release/0.25'2023-12-20T14:49:54ZRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comCherry-pick: Merge branch 'gc-fix-cache' into 'release/0.25'Original MR: https://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/462
## Type of change
- [x] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does ...Original MR: https://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/462
## 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?
- [ ] AWS
- [ ] Azure
- [x] Google Cloud
- [ ] IBM
## Does this introduce a breaking change?
- [NO]M22 - Release 0.25Rustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comhttps://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/469Cherry-pick '[MSCOSDU-1851] fix json, io.netty, reactor-core vulnerabilities'...2023-12-13T09:01:50ZDavid Diederichd.diederich@opengroup.orgCherry-pick '[MSCOSDU-1851] fix json, io.netty, reactor-core vulnerabilities' into release/0.25**Original MR**: !465
### 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**: !465
### 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/notification/-/pipelines/new?ref=cherry-pick-for-465)M22 - Release 0.25David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.org