Notification merge requestshttps://community.opengroup.org/osdu/platform/system/notification/-/merge_requests2023-08-18T15:24:10Zhttps://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/285GONRG-5890-Change-to-GC2023-08-18T15:24:10ZEldor Pulatov [EPAM/GCP]GONRG-5890-Change-to-GC## Type of change
- [ ] Bug Fix
- [ ] Feature
**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 p...## Type of change
- [ ] Bug Fix
- [ ] Feature
**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
- [ ] Azure
- [x] GCP
- [ ] IBM
## Does this introduce a breaking change?
- [YES/NO]
## What is the current behavior?
## What is the new/expected behavior?
## Have you added/updated Unit Tests and Integration Tests?
## Any other useful informationM15 - Release 0.18Eldor Pulatov [EPAM/GCP]Eldor Pulatov [EPAM/GCP]https://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/281fix whitesource vulnerabilities2023-03-23T19:03:16ZYauheni Lesnikaufix whitesource vulnerabilitiesFix next whitesource vulnerabilities for the notificatiom-core and notification-azure:
jackson-databind - CVE-2020-36518, CVE-2022-42004, CVE-2022-42003
undertow-core - CVE-2020-36518, CVE-2021-3859
spring-security-web - CVE-2022-229...Fix next whitesource vulnerabilities for the notificatiom-core and notification-azure:
jackson-databind - CVE-2020-36518, CVE-2022-42004, CVE-2022-42003
undertow-core - CVE-2020-36518, CVE-2021-3859
spring-security-web - CVE-2022-22978
spring-beans - CVE-2022-22965
google-oauth-client - CVE-2021-22573
json - WS-2017-3805
snakeyaml - CVE-2022-25857M15 - Release 0.18Yauheni LesnikauYauheni Lesnikauhttps://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/273Removed google cloud libs from the core part.2022-11-03T11:17:13ZRiabokon Stanislav(EPAM)[GCP]Removed google cloud libs from the core part.## Type of change
- [x] Bug Fix
- [ ] Feature
https://community.opengroup.org/osdu/platform/system/notification/-/issues/50
## Does this introduce a change in the core logic?
- [YES]
## Does this introduce a change in the cloud provi...## Type of change
- [x] Bug Fix
- [ ] Feature
https://community.opengroup.org/osdu/platform/system/notification/-/issues/50
## Does this introduce a change in the core logic?
- [YES]
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [x] AWS
- [x] Azure
- [x] GCP
- [x] IBM
## Does this introduce a breaking change?
- [YES]
Removed GCP cloud libs from Core Part.M15 - Release 0.18Riabokon Stanislav(EPAM)[GCP]Riabokon Stanislav(EPAM)[GCP]https://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/269Upgrade First Party Library Dependencies for Release 0.172022-10-07T12:15:51ZDavid Diederichd.diederich@opengroup.orgUpgrade First Party Library Dependencies for Release 0.17This automated 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 automated 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: 45145af65ff72876217458186a80096fed97a4ca
Maven: 0.17.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------------------------------------------- | ---------------------- | -------------- |
| core-lib-azure | 0.16.0-rc5 | 0.0.22 |
| core-lib-gcp | 0.16.0 | |
| core-test-lib-gcp | | 0.0.2 |
| os-core-lib-aws | 0.14.0 | 0.14.0-rc2 |
| obm | 0.16.0 | |
| oqm | 0.16.0 | |
| os-core-common | 0.14.0 | 0.3.4, 0.3.6 |
| os-core-lib-ibm | 0.16.0-rc1 | 0.15.2 |
| osm | 0.16.0 | |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.13.2.2 | 2.13.2.2 |
| (3rd Party) org.apache.logging.log4j.log4j-api | 2.17.1 | 2.12.1, 2.11.1 |
| (3rd Party) org.apache.logging.log4j.log4j-core | 2.17.1 | 2.12.1 |
| (3rd Party) org.apache.logging.log4j.log4j-jul | 2.17.1 | 2.12.1 |
| (3rd Party) org.apache.logging.log4j.log4j-slf4j-impl | 2.17.1 | 2.12.1 |
| (3rd Party) org.apache.logging.log4j.log4j-to-slf4j | 2.17.1 | 2.11.2, 2.13.3 |
| (3rd Party) org.springframework.spring-webflux | 5.3.12 | |
| (3rd Party) org.springframework.spring-webmvc | 5.1.19.RELEASE, 5.3.22 | 5.1.9.RELEASE |
```
Warning: Found Vulnerable Spring MVC dependency (<5.2.20 || >=5.3.0 <5.3.18)
├─ _Root_
│ ├─ org.opengroup.osdu.notification-core == 0.17.0-SNAPSHOT
│ │ └─ org.springframework.boot.spring-boot-starter-web == 2.1.7.RELEASE
│ │ └─ org.springframework.spring-webmvc == 5.1.19.RELEASE
│ ├─ org.opengroup.osdu.notification-gcp == 0.17.0-SNAPSHOT
│ │ └─ org.opengroup.osdu.os-core-common == 0.14.0
│ │ └─ org.springframework.boot.spring-boot-starter-web == 2.1.18.RELEASE
│ │ └─ org.springframework.spring-webmvc == 5.1.19.RELEASE
│ └─ org.opengroup.osdu.notification-ibm == 0.17.0-SNAPSHOT
│ └─ org.opengroup.osdu.notification-core == 0.17.0-SNAPSHOT
│ └─ org.springframework.boot.spring-boot-starter-web == 2.1.18.RELEASE
│ └─ org.springframework.spring-webmvc == 5.1.19.RELEASE
└─ testing/
├─ org.opengroup.osdu.notification.notification-test-core == 0.17.0-SNAPSHOT
│ └─ org.opengroup.osdu.os-core-common == 0.3.4
│ └─ org.springframework.boot.spring-boot-starter-web == 2.1.7.RELEASE
│ └─ org.springframework.spring-webmvc == 5.1.9.RELEASE
├─ org.opengroup.osdu.notification-test-azure == 0.17.0-SNAPSHOT
│ └─ org.opengroup.osdu.notification.notification-test-core == 0.17.0-SNAPSHOT
│ └─ org.opengroup.osdu.os-core-common == 0.3.4
│ └─ org.springframework.boot.spring-boot-starter-web == 2.1.7.RELEASE
│ └─ org.springframework.spring-webmvc == 5.1.9.RELEASE
├─ org.opengroup.osdu.notification-test-gcp == 0.17.0-SNAPSHOT
│ └─ org.opengroup.osdu.os-core-common == 0.3.6
│ └─ org.springframework.boot.spring-boot-starter-web == 2.1.7.RELEASE
│ └─ org.springframework.spring-webmvc == 5.1.9.RELEASE
├─ org.opengroup.osdu.notification-test-aws == 0.17.0-SNAPSHOT
│ └─ org.opengroup.osdu.os-core-common == 0.3.6
│ └─ org.springframework.boot.spring-boot-starter-web == 2.1.7.RELEASE
│ └─ org.springframework.spring-webmvc == 5.1.9.RELEASE
├─ org.opengroup.osdu.notification-test-ibm == 0.17.0-SNAPSHOT
│ └─ org.opengroup.osdu.os-core-common == 0.3.6
│ └─ org.springframework.boot.spring-boot-starter-web == 2.1.7.RELEASE
│ └─ org.springframework.spring-webmvc == 5.1.9.RELEASE
└─ org.opengroup.osdu.notification-test-anthos == 0.17.0-SNAPSHOT
└─ org.opengroup.osdu.os-core-common == 0.3.6
└─ org.springframework.boot.spring-boot-starter-web == 2.1.7.RELEASE
└─ org.springframework.spring-webmvc == 5.1.9.RELEASE
```
```
Warning: Found Vulnerable Spring WebFlux dependency (<5.2.20 || >=5.3.0 <5.3.18)
└─ _Root_
└─ org.opengroup.osdu.notification-azure == 0.17.0-SNAPSHOT
└─ com.azure.spring.azure-spring-boot-starter-active-directory == 3.4.0
└─ org.springframework.boot.spring-boot-starter-webflux == 2.5.12
└─ org.springframework.spring-webflux == 5.3.12
```
### Dependency Information After the Upgrade
```
Branch: dependency-upgrade
SHA: f62c20fee7b788c4351b67b947a44f45250644c2
Maven: 0.17.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------------------------------------------- | ---------------------- | -------------- |
| core-lib-azure | 0.16.0-rc5 | 0.0.22 |
| core-lib-gcp | 0.17.0 | |
| core-test-lib-gcp | | 0.0.2 |
| os-core-lib-aws | 0.14.0 | 0.14.0-rc2 |
| obm | 0.17.0 | |
| oqm | 0.17.0 | |
| os-core-common | 0.14.0 | 0.3.4, 0.3.6 |
| os-core-lib-ibm | 0.16.0-rc1 | 0.15.2 |
| osm | 0.17.0 | |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.13.2.2 | 2.13.2.2 |
| (3rd Party) org.apache.logging.log4j.log4j-api | 2.17.1 | 2.12.1, 2.11.1 |
| (3rd Party) org.apache.logging.log4j.log4j-core | 2.17.1 | 2.12.1 |
| (3rd Party) org.apache.logging.log4j.log4j-jul | 2.17.1 | 2.12.1 |
| (3rd Party) org.apache.logging.log4j.log4j-slf4j-impl | 2.17.1 | 2.12.1 |
| (3rd Party) org.apache.logging.log4j.log4j-to-slf4j | 2.17.1 | 2.11.2, 2.13.3 |
| (3rd Party) org.springframework.spring-webflux | 5.3.12 | |
| (3rd Party) org.springframework.spring-webmvc | 5.1.19.RELEASE, 5.3.22 | 5.1.9.RELEASE |
```
Warning: Found Vulnerable Spring MVC dependency (<5.2.20 || >=5.3.0 <5.3.18)
├─ _Root_
│ ├─ org.opengroup.osdu.notification-core == 0.17.0-SNAPSHOT
│ │ └─ org.springframework.boot.spring-boot-starter-web == 2.1.7.RELEASE
│ │ └─ org.springframework.spring-webmvc == 5.1.19.RELEASE
│ ├─ org.opengroup.osdu.notification-gcp == 0.17.0-SNAPSHOT
│ │ └─ org.opengroup.osdu.os-core-common == 0.14.0
│ │ └─ org.springframework.boot.spring-boot-starter-web == 2.1.18.RELEASE
│ │ └─ org.springframework.spring-webmvc == 5.1.19.RELEASE
│ └─ org.opengroup.osdu.notification-ibm == 0.17.0-SNAPSHOT
│ └─ org.opengroup.osdu.notification-core == 0.17.0-SNAPSHOT
│ └─ org.springframework.boot.spring-boot-starter-web == 2.1.18.RELEASE
│ └─ org.springframework.spring-webmvc == 5.1.19.RELEASE
└─ testing/
├─ org.opengroup.osdu.notification.notification-test-core == 0.17.0-SNAPSHOT
│ └─ org.opengroup.osdu.os-core-common == 0.3.4
│ └─ org.springframework.boot.spring-boot-starter-web == 2.1.7.RELEASE
│ └─ org.springframework.spring-webmvc == 5.1.9.RELEASE
├─ org.opengroup.osdu.notification-test-azure == 0.17.0-SNAPSHOT
│ └─ org.opengroup.osdu.notification.notification-test-core == 0.17.0-SNAPSHOT
│ └─ org.opengroup.osdu.os-core-common == 0.3.4
│ └─ org.springframework.boot.spring-boot-starter-web == 2.1.7.RELEASE
│ └─ org.springframework.spring-webmvc == 5.1.9.RELEASE
├─ org.opengroup.osdu.notification-test-gcp == 0.17.0-SNAPSHOT
│ └─ org.opengroup.osdu.os-core-common == 0.3.6
│ └─ org.springframework.boot.spring-boot-starter-web == 2.1.7.RELEASE
│ └─ org.springframework.spring-webmvc == 5.1.9.RELEASE
├─ org.opengroup.osdu.notification-test-aws == 0.17.0-SNAPSHOT
│ └─ org.opengroup.osdu.os-core-common == 0.3.6
│ └─ org.springframework.boot.spring-boot-starter-web == 2.1.7.RELEASE
│ └─ org.springframework.spring-webmvc == 5.1.9.RELEASE
├─ org.opengroup.osdu.notification-test-ibm == 0.17.0-SNAPSHOT
│ └─ org.opengroup.osdu.os-core-common == 0.3.6
│ └─ org.springframework.boot.spring-boot-starter-web == 2.1.7.RELEASE
│ └─ org.springframework.spring-webmvc == 5.1.9.RELEASE
└─ org.opengroup.osdu.notification-test-anthos == 0.17.0-SNAPSHOT
└─ org.opengroup.osdu.os-core-common == 0.3.6
└─ org.springframework.boot.spring-boot-starter-web == 2.1.7.RELEASE
└─ org.springframework.spring-webmvc == 5.1.9.RELEASE
```
```
Warning: Found Vulnerable Spring WebFlux dependency (<5.2.20 || >=5.3.0 <5.3.18)
└─ _Root_
└─ org.opengroup.osdu.notification-azure == 0.17.0-SNAPSHOT
└─ com.azure.spring.azure-spring-boot-starter-active-directory == 3.4.0
└─ org.springframework.boot.spring-boot-starter-webflux == 2.5.12
└─ org.springframework.spring-webflux == 5.3.12
```M15 - Release 0.18Riabokon Stanislav(EPAM)[GCP]Riabokon Stanislav(EPAM)[GCP]https://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/350Cherry-pick 'Removed test validations on cors response headers' into release/...2023-02-16T17:36:53ZManish JangidCherry-pick 'Removed test validations on cors response headers' into release/0.19Original MR: !349
## Type of change
- [ ] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a change in the core logic?
- [YES/NO] No
## Does this introduce a...Original MR: !349
## Type of change
- [ ] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a change in the core logic?
- [YES/NO] 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?
- [YES/NO] No
## What is the current behavior?
## What is the new/expected behavior?
## Have you added/updated Unit Tests and Integration Tests? Fixed failing tests
## Any other useful informationM16 - Release 0.19https://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/349Removed test validations on cors response headers2023-02-16T14:55:54ZManish JangidRemoved test validations on cors response headers## Type of change
- [ ] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a change in the core logic?
- [YES/NO] No
## Does this introduce a change in the clou...## Type of change
- [ ] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a change in the core logic?
- [YES/NO] 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?
- [YES/NO] No
## What is the current behavior?
## What is the new/expected behavior?
## Have you added/updated Unit Tests and Integration Tests? Fixed test cases for AWS
## Any other useful informationM16 - Release 0.19https://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/346Cherry-pick 'Adding retry for jersey client for Azure ITs in case of 502 and ...2023-02-15T10:26:59ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Adding retry for jersey client for Azure ITs in case of 502 and 503.' into release/0.19**Original MR**: !316
### 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**: !316
### 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-316)M16 - Release 0.19David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/344Cherry-pick 'adding support for EKS 1.23' into release/0.192023-02-11T01:56:14ZMarc Burnie [AWS]Cherry-pick 'adding support for EKS 1.23' into release/0.19Original MR: https://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/342
Only AWS Helm Chart changes.Original MR: https://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/342
Only AWS Helm Chart changes.M16 - Release 0.19David Diederichd.diederich@opengroup.orgMarc Burnie [AWS]David Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/342Adding support for EKS 1.232023-02-10T21:07:20ZMarc Burnie [AWS]Adding support for EKS 1.23M16 - Release 0.19Marc Burnie [AWS]Marc Burnie [AWS]https://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/339Upgrade First Party Library Dependencies for Release 0.192023-02-18T07:31:18ZDavid Diederichd.diederich@opengroup.orgUpgrade First Party Library Dependencies for Release 0.19This automated 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 automated 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: 13844b414cc330f8d6228cb2129181d76a5b1f86
Maven: 0.20.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------------------------------------------- | ---------------- | -------------- |
| core-lib-azure | 0.19.0-rc8 | 0.12.0-rc10 |
| core-lib-gcp | 0.19.0-rc3 | |
| core-test-lib-gcp | | 0.0.2 |
| os-core-lib-aws | 0.19.0-rc3 | 0.14.0-rc2 |
| obm | 0.18.0 | |
| oqm | 0.18.0 | |
| os-core-common | 0.19.0-rc6 | 0.3.4, 0.3.6 |
| os-core-lib-ibm | 0.16.0-rc1 | 0.15.2 |
| osm | 0.18.0 | |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.14.1, 2.13.2.2 | 2.13.2.2 |
| (3rd Party) net.minidev.json-smart | 2.4.7 | 2.4.6 |
| (3rd Party) org.apache.logging.log4j.log4j-api | 2.17.1 | 2.13.3, 2.11.1 |
| (3rd Party) org.apache.logging.log4j.log4j-core | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-jul | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-slf4j-impl | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-to-slf4j | 2.17.1 | 2.11.2, 2.13.3 |
| (3rd Party) org.springframework.spring-webflux | 5.3.24 | |
| (3rd Party) org.springframework.spring-webmvc | 5.3.24 | 5.1.9.RELEASE |
### Dependency Information After the Upgrade
```
Branch: dependency-upgrade
SHA: 4afa989dcbb0b46d33127d3f124f010046f6bdf1
Maven: 0.20.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------------------------------------------- | ---------------- | -------------- |
| core-lib-azure | 0.19.0 | 0.12.0-rc10 |
| core-lib-gcp | 0.19.0 | |
| core-test-lib-gcp | | 0.0.2 |
| os-core-lib-aws | 0.19.0 | 0.14.0-rc2 |
| obm | 0.19.0 | |
| oqm | 0.19.0 | |
| os-core-common | 0.19.0 | 0.3.4, 0.3.6 |
| os-core-lib-ibm | 0.16.0-rc1 | 0.15.2 |
| osm | 0.19.0 | |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.14.1, 2.13.2.2 | 2.13.2.2 |
| (3rd Party) net.minidev.json-smart | 2.4.7 | 2.4.6 |
| (3rd Party) org.apache.logging.log4j.log4j-api | 2.17.1 | 2.13.3, 2.11.1 |
| (3rd Party) org.apache.logging.log4j.log4j-core | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-jul | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-slf4j-impl | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-to-slf4j | 2.17.1 | 2.11.2, 2.13.3 |
| (3rd Party) org.springframework.spring-webflux | 5.3.24 | |
| (3rd Party) org.springframework.spring-webmvc | 5.3.24 | 5.1.9.RELEASE |M16 - Release 0.19https://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/337Added redis service for notification in GC2023-02-03T16:09:34ZSiarhei Symanovich (EPAM)Added redis service for notification in GC## Type of change
- [ ] Bug Fix
- [x] 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
- [ ] Bug Fix
- [x] 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]
## What is the current behavior?
Notification works without redis
## What is the new/expected behavior?
Notification will work with redis
## Have you added/updated Unit Tests and Integration Tests?
## Any other useful informationM16 - Release 0.19Siarhei Symanovich (EPAM)Siarhei Symanovich (EPAM)https://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/336added x-collaboration property to the message header.2023-07-04T11:12:51ZAnfal Fadhiladded x-collaboration property to the message header.## Type of change
- [x] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
https://community.opengroup.org/osdu/platform/system/storage/-/issues/149
## Does this introduce a change in...## Type of change
- [x] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
https://community.opengroup.org/osdu/platform/system/storage/-/issues/149
## Does this introduce a change in the core logic?
- [NO]
## Does this introduce a breaking change?
- [NO]
## What is the current behavior?
no "x-collaboration" property sent in the message header.
## What is the new/expected behavior?
"x-collaboration" property returned in the message header.M16 - Release 0.19Anfal FadhilAnfal Fadhilhttps://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/333GCP Reworked notification logic (GONRG-5700)2023-01-27T18:34:04ZDmitrii Novikov (EPAM)GCP Reworked notification logic (GONRG-5700)## Type of change
- [ ] Bug Fix
- [x] Feature
https://kb.epam.com/display/GONRG/OSDU+Notification+service+archtecture+proposal?moved=true
## Does this introduce a change in the core logic?
- [NO]
## Does this introduce a change in th...## Type of change
- [ ] Bug Fix
- [x] Feature
https://kb.epam.com/display/GONRG/OSDU+Notification+service+archtecture+proposal?moved=true
## 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?
- [YES]
## What is the new/expected behavior?
1. Third-party subscriber subscribes/unsubscribes for specific OSDU events notifications via the Register service REST API
2. Register service publishes registration/unregistration info via the register-subscriber-control topic/exchange
3. Notification service instances process single (statically defined) subscription/queue to obtain registration info changes
4. Notification service instances persists/reads registration info in the shared database/cache.
5. OSDU services (Storage, Schema etc.) publish their events through corresponding topics/exchanges (records-changed, schema-changed etc.)
6. Notification service instances concurrently process single subscription/queue, statically defined per each original topic/exchange
7. Notification service publishes N (N is the number of third-party subscribtions) outgoing messages via the corresponding *-notification topic/exchange (example: records-changed-notification for records changed events). Each outgoing event is the original event enriched with the destination information (subscriber id). The original event is properly acknowledged upon end of processing.
7a. RabbitMQ: *-notification exchange should be a delayed exchange (type x-delayed-message), which requires special RabbitMQ rabbitmq_delayed_message_exchange plugin installed
7b. RabbitMQ: the outgoing event contains no x-delay header to be processed w/o time delay
8. Notification service instances concurrently process single subscription/queue, statically defined per each outgoing topic/exchange
9. Notification service collects corresponding subscription info from the DB (4) or distributed cache and sends notification (HTTP call to the endpoint) to the third-party subscriber. In case of successful call the outgoing message is properly acknowledged. In case of notification failure (third-party endpoint not available for instance) the following should be performed to provide notification delivery retry logic:
9a. GCP PubSub: the outgoing message is NACK-ed and then re-delivered after configured back-off time in accordance with Retry policy
9b. RabbitMQ: the outgoing message is ACK-ed and re-published (7) in the the corresponding *-notification exchange with x-delay and x-retries headers to be re-processed with time delay. If x-retries already present in the processed message header it's value should be incremented. If x-retries value equals to configured limit of retries, the message is not re-published. In further implementations it may be routed to dead letter queue (out of scope for now)M16 - Release 0.19Dmitrii Novikov (EPAM)Dmitrii Novikov (EPAM)https://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/332fix whitesource issues for azure module2023-07-04T11:11:11ZYauheni Lesnikaufix whitesource issues for azure moduleFix library security vulnerabilities in azure moduleFix library security vulnerabilities in azure moduleM16 - Release 0.19Yauheni LesnikauYauheni Lesnikauhttps://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/331Collaboration Support documentation update2023-07-04T11:14:58ZAnfal FadhilCollaboration Support documentation update
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
[ADR](https://community.opengroup.org/groups/osdu/platform/system/-/wikis/Feature-Flag)
## Does this introduce a change in the core logic?
- [NO]
## Does t...
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
[ADR](https://community.opengroup.org/groups/osdu/platform/system/-/wikis/Feature-Flag)
## Does this introduce a change in the core logic?
- [NO]
## Does this introduce a breaking change?
- [NO]
## What is the current behavior?
Collaboration support is not mentioned in the docs.
## What is the new/expected behavior?
Added Collaboration Support documentation.M16 - Release 0.19Anfal FadhilAnfal Fadhilhttps://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/330Update core common and vulnerable libs version2023-08-18T15:24:09ZManish JangidUpdate core common and vulnerable libs version## Type of change
- [x] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
For openApi migration, related ISSUE: https://community.opengroup.org/osdu/platform/system/indexer-service/-/i...## Type of change
- [x] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
For openApi migration, related ISSUE: https://community.opengroup.org/osdu/platform/system/indexer-service/-/issues/74
## Does this introduce a change in the core logic?
- [YES/NO] No
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [ ] Azure
- [ ] Google Cloud
- [ ] IBM
## Does this introduce a breaking change?
- [YES/NO]No
## What is the current behavior?
## What is the new/expected behavior? No change in behavior
## Have you added/updated Unit Tests and Integration Tests? No
## Any other useful information
* Updating versions of vulnerable libraries
* Using latest version of core common lib which has Spring boot 2.7.7
* Migration from Springfox to springdoc-openapi.M16 - Release 0.19https://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/329Fix spring vulnerabilities2023-02-20T11:57:40ZManish JangidFix spring vulnerabilities## 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?
- [YES/NO]
## Does this introduce a change in the cloud p...## 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?
- [YES/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?
- [YES/NO] No
## What is the current behavior?
## What is the new/expected behavior?
## Have you added/updated Unit Tests and Integration Tests?
## Any other useful informationM16 - Release 0.19https://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/327Removed aud (GONRG-6303)2023-01-17T13:23:55ZRiabokon Stanislav(EPAM)[GCP]Removed aud (GONRG-6303)## Type of change
- [ ] Bug Fix
- [x] Feature
## 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
- [ ] Azure
- [x] Google C...## Type of change
- [ ] Bug Fix
- [x] Feature
## 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
- [ ] Azure
- [x] Google Cloud
- [ ] IBM
## Does this introduce a breaking change?
- [NO]
-
## What is the new/expected behavior?
Removed aud from module.M16 - Release 0.19Riabokon Stanislav(EPAM)[GCP]Riabokon Stanislav(EPAM)[GCP]https://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/326fixing dependency check2023-01-09T16:51:04ZMarc Burnie [AWS]fixing dependency checkM16 - Release 0.19Marc Burnie [AWS]Marc Burnie [AWS]https://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/323temporarily bypass maven dependency check2023-01-09T14:47:49ZMorris Estepatemporarily bypass maven dependency checkM16 - Release 0.19Morris EstepaMorris Estepa