Notification merge requestshttps://community.opengroup.org/osdu/platform/system/notification/-/merge_requests2023-04-17T22:44:07Zhttps://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/375Cherry pick changes from M14 to M16 master branch2023-04-17T22:44:07ZVaibhavi KamaniCherry pick changes from M14 to M16 master branchCherry pick changes from M14 to M16 master branchCherry pick changes from M14 to M16 master branchVaibhavi KamaniVaibhavi Kamanihttps://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/374remove logs that cause logs quota exhaustion2023-04-19T14:03:23ZYurii Kondakovremove logs that cause logs quota exhaustionHOTFIX. We saw log quota exhaustion in prod. The biggest culprit was notification service traces. We have identified 3 log entries that appear to be causing the bulk of the issues and these should be removed
1. Log message startswith "N...HOTFIX. We saw log quota exhaustion in prod. The biggest culprit was notification service traces. We have identified 3 log entries that appear to be causing the bulk of the issues and these should be removed
1. Log message startswith "Notification process started for message with id" - from **notification** service
2. Log message startswith "Start worker task : {messageId" - from core-lib-azure
3. Log message startswith "End worker task duration(ms)" from core-lib-azure
core-lib-azure logs(2,3) will be removed by MR
https://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/294M18 - Release 0.21Yurii KondakovYurii Kondakovhttps://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/373Updating NOTICE2023-04-13T14:00:05ZChad LeongUpdating NOTICEFIX NOTICEFIX NOTICEM17 - Release 0.20https://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/372Merge branch 'gc-unhardcode-groupid-in-it' into 'master'2023-04-13T20:54:29ZRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comMerge branch 'gc-unhardcode-groupid-in-it' into 'master'Original merge https://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/370
## Type of change
- [x] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
-
## Do...Original merge https://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/370
## 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]
## What is the current behavior?
Group id is hardcoded in int tests.
## What is the new/expected behavior?
Group id can be configured via env vars.
## Have you added/updated Unit Tests and Integration Tests?
-
## Any other useful information
-M17 - Release 0.20Rustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comhttps://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/371GONRG-6935: Bring GROUP_ID variable to notification service2023-04-12T12:49:00ZMaksym Petrenko [EPAM / GCP]GONRG-6935: Bring GROUP_ID variable to notification service## 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
- [ ] Google Cloud
- [ ] 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 informationMaksym Petrenko [EPAM / GCP]Maksym Petrenko [EPAM / GCP]https://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/370unhardcode group id in it2023-04-13T16:44:35ZRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comunhardcode group id in it## 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?
- [ ] AWS
- [ ] Azure
- [x] Google Cloud
- [ ] IBM
## Does this introduce a breaking change?
- [NO]
## What is the current behavior?
Group id is hardcoded in int tests.
## What is the new/expected behavior?
Group id can be configured via env vars.
## Have you added/updated Unit Tests and Integration Tests?
-
## Any other useful information
-M17 - Release 0.20Rustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comhttps://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/369Full Upgrade of First Party Library Dependencies for Release 0.202023-05-22T15:50:25ZDavid Diederichd.diederich@opengroup.orgFull Upgrade of First Party Library Dependencies for Release 0.20This generated MR upgrades the first party libraries (other OSDU libraries) to utilize the latest release.
The intent is to try to fully upgrade all dependent libraries to see if the latest code will work.
It is expected that these will ...This generated MR upgrades the first party libraries (other OSDU libraries) to utilize the latest release.
The intent is to try to fully upgrade all dependent libraries to see if the latest code will work.
It is expected that these will often fail, since the upgrades were previously rejected for failing pipelines and have not been directly addressed yet.
This 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.
This MR may co-exist with a separate, smaller upgrade MR.
If both pass, this one should be used instead.
### Dependency Information Before the Upgrade
```
Branch: master
SHA: c90ffd91938b16d47f7037f8c3afb15c396aab99
Maven: 0.21.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ----------------------------------------------------- | ---------- | -------------- |
| core-lib-azure | 0.19.0-rc8 | 0.12.0-rc10 |
| core-lib-gcp | 0.20.0-rc1 | |
| core-test-lib-gcp | | 0.0.2 |
| os-core-lib-aws | 0.21.0-rc1 | 0.14.0-rc2 |
| obm | 0.19.0 | |
| oqm | 0.19.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.20.0-rc2 | |
| (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-webmvc | 5.3.24 | 5.1.9.RELEASE |
| (3rd Party) org.yaml.snakeyaml | 1.30, 1.33 | 1.23, 1.27 |
```
Critical: Found Vulnerable Snake YAML dependency (<2.0)
├─ _Root_
│ ├─ org.projectlombok.lombok == 1.18.8
│ │ └─ org.springdoc.springdoc-openapi-ui == 1.6.9
│ │ └─ org.springdoc.springdoc-openapi-webmvc-core == 1.6.9
│ │ └─ org.springdoc.springdoc-openapi-common == 1.6.9
│ │ └─ io.swagger.core.v3.swagger-core == 2.2.0
│ │ └─ com.fasterxml.jackson.dataformat.jackson-dataformat-yaml == 2.13.4
│ │ └─ org.yaml.snakeyaml == 1.30
│ ├─ org.opengroup.osdu.notification-core == 0.21.0-SNAPSHOT
│ │ └─ org.springframework.boot.spring-boot-starter-web == 2.7.7
│ │ └─ org.springframework.boot.spring-boot-starter == 2.7.7
│ │ └─ org.yaml.snakeyaml == 1.33
│ ├─ org.opengroup.osdu.notification-gc == 0.21.0-SNAPSHOT
│ │ └─ org.opengroup.osdu.os-core-common == 0.19.0-rc6
│ │ └─ 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.notification-azure == 0.21.0-SNAPSHOT
│ │ └─ org.opengroup.osdu.core-lib-azure == 0.19.0-rc8
│ │ └─ org.redisson.redisson == 3.15.3
│ │ └─ org.yaml.snakeyaml == 1.33
│ ├─ org.opengroup.osdu.notification-ibm == 0.21.0-SNAPSHOT
│ │ └─ org.yaml.snakeyaml == 1.33
│ └─ org.opengroup.osdu.notification-aws == 0.21.0-SNAPSHOT
│ └─ org.springframework.boot.spring-boot-starter-actuator == 2.7.7
│ └─ org.springframework.boot.spring-boot-starter == 2.7.7
│ └─ org.yaml.snakeyaml == 1.33
└─ testing/
├─ org.opengroup.osdu.notification.notification-test-core == 0.21.0-SNAPSHOT
│ └─ org.opengroup.osdu.os-core-common == 0.3.4
│ └─ org.springframework.boot.spring-boot-starter-web == 2.1.7.RELEASE
│ └─ org.springframework.boot.spring-boot-starter == 2.1.7.RELEASE
│ └─ org.yaml.snakeyaml == 1.23
├─ org.opengroup.osdu.notification-test-azure == 0.21.0-SNAPSHOT
│ └─ org.opengroup.osdu.core-lib-azure == 0.12.0-rc10
│ └─ org.springframework.boot.spring-boot-starter-aop == 2.4.5
│ └─ org.springframework.boot.spring-boot-starter == 2.4.5
│ └─ org.yaml.snakeyaml == 1.27
├─ org.opengroup.osdu.notification-test-gc == 0.21.0-SNAPSHOT
│ └─ org.opengroup.osdu.os-core-common == 0.3.6
│ └─ org.springframework.boot.spring-boot-starter-web == 2.1.7.RELEASE
│ └─ org.springframework.boot.spring-boot-starter == 2.1.7.RELEASE
│ └─ org.yaml.snakeyaml == 1.23
├─ org.opengroup.osdu.notification-test-aws == 0.21.0-SNAPSHOT
│ └─ org.opengroup.osdu.os-core-common == 0.3.6
│ └─ org.springframework.boot.spring-boot-starter-web == 2.1.7.RELEASE
│ └─ org.springframework.boot.spring-boot-starter == 2.1.7.RELEASE
│ └─ org.yaml.snakeyaml == 1.23
├─ org.opengroup.osdu.notification-test-ibm == 0.21.0-SNAPSHOT
│ └─ org.opengroup.osdu.os-core-lib-ibm == 0.15.2
│ └─ org.springframework.boot.spring-boot-starter-security == 2.4.5
│ └─ org.springframework.boot.spring-boot-starter == 2.4.5
│ └─ org.yaml.snakeyaml == 1.27
└─ org.opengroup.osdu.notification-test-anthos == 0.21.0-SNAPSHOT
└─ org.opengroup.osdu.os-core-common == 0.3.6
└─ org.springframework.boot.spring-boot-starter-web == 2.1.7.RELEASE
└─ org.springframework.boot.spring-boot-starter == 2.1.7.RELEASE
└─ org.yaml.snakeyaml == 1.23
```
### Dependency Information After the Upgrade
```
Branch: dependency-upgrade
SHA: 9c87f102a8a3475be8b04e54ad05f69b23a05fc3
Maven: 0.21.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| --------------------------------------------------- | --------------- | --------------- |
| core-lib-azure | 0.20.0 | 0.20.0 |
| core-lib-gc | 0.20.0 | |
| core-test-lib-gcp | | 0.20.0 |
| os-core-lib-aws | 0.21.0-rc2 | 0.21.0-rc2 |
| obm | 0.20.0 | |
| oqm | 0.20.0 | |
| os-core-common | 0.20.1 | 0.20.1 |
| os-core-lib-ibm | 0.20.0 | 0.20.0 |
| osm | 0.20.0 | |
| (3rd Party) org.apache.logging.log4j.log4j-api | 2.17.1 | 2.17.2, 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-to-slf4j | 2.17.1 | 2.17.2, 2.13.3 |
| (3rd Party) org.yaml.snakeyaml | 1.30, 2.0, 1.33 | 1.30, 1.27, 2.0 |
```
Critical: Found Vulnerable Snake YAML dependency (<2.0)
├─ _Root_
│ ├─ org.projectlombok.lombok == 1.18.8
│ │ └─ org.springdoc.springdoc-openapi-ui == 1.6.9
│ │ └─ org.springdoc.springdoc-openapi-webmvc-core == 1.6.9
│ │ └─ org.springdoc.springdoc-openapi-common == 1.6.9
│ │ └─ io.swagger.core.v3.swagger-core == 2.2.0
│ │ └─ com.fasterxml.jackson.dataformat.jackson-dataformat-yaml == 2.13.4
│ │ └─ org.yaml.snakeyaml == 1.30
│ ├─ org.opengroup.osdu.notification-gc == 0.21.0-SNAPSHOT
│ │ └─ org.opengroup.osdu.os-core-common == 0.20.1
│ │ └─ 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.notification-ibm == 0.21.0-SNAPSHOT
│ └─ org.yaml.snakeyaml == 1.33
└─ testing/
├─ org.opengroup.osdu.notification.notification-test-core == 0.21.0-SNAPSHOT
│ └─ org.opengroup.osdu.os-core-common == 0.20.1
│ └─ 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.notification-test-azure == 0.21.0-SNAPSHOT
│ └─ org.opengroup.osdu.core-lib-azure == 0.20.0
│ └─ org.redisson.redisson == 3.15.3
│ └─ org.yaml.snakeyaml == 1.27
├─ org.opengroup.osdu.notification-test-gc == 0.21.0-SNAPSHOT
│ └─ org.opengroup.osdu.os-core-common == 0.20.1
│ └─ 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.notification-test-aws == 0.21.0-SNAPSHOT
│ └─ org.opengroup.osdu.core.aws.os-core-lib-aws == 0.21.0-rc2
│ └─ 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.notification-test-anthos == 0.21.0-SNAPSHOT
└─ org.opengroup.osdu.os-core-common == 0.20.1
└─ 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.21Srinivasan NarayananSrinivasan Narayananhttps://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/368OpenAPI 3.0 Documentation using springdoc2023-04-12T03:04:27ZThulasi Dass SubramanianOpenAPI 3.0 Documentation using springdoc
**Link to ADR(Architecture Decision Record)** : [Swagger using springdoc-openapi](https://community.opengroup.org/osdu/platform/system/home/-/issues/97)
## OpenAPI 3.0 related changes
* upgraded to latest **springdoc openapi** latest ...
**Link to ADR(Architecture Decision Record)** : [Swagger using springdoc-openapi](https://community.opengroup.org/osdu/platform/system/home/-/issues/97)
## OpenAPI 3.0 related changes
* upgraded to latest **springdoc openapi** latest version [1.6.14](https://mvnrepository.com/artifact/org.springdoc/springdoc-openapi-ui/1.6.14)
* used **[@OpenAPIDefinition](https://docs.swagger.io/swagger-core/v2.0.9/apidocs/io/swagger/v3/oas/annotations/OpenAPIDefinition.html)** annotation to populate OpenAPI Object fields *\[info, tags, servers, security\]*
* Documented the below API's with OpenAPI 3.0 **Annotations**
- PubSubEndpoint API
- Health Checks API
- Info API
* Added the standard HTTP Response(4xx, 5x\*\*\*\*x) for API Responses
* Custom Path for
* **Swagger UI**: https://host/context-path/swagger (will redirect to https://host/context-path/swagger-ui/index.html)
* **api-docs (JSON)** : https://host/context-path/api-docs
* **api-docs (YAML)** : https://host/context-path/api-docs.yaml
* Azure Swagger GLAB(for Reference)
* **Swagger UI**: https://osdu-glab.msft-osdu-test.org/api/notification/v1/swagger (will redirect to https://osdu-glab.msft-osdu-test.org/api/notification/v1/swagger-ui/index.html)
* **api-docs (JSON)** : https://osdu-glab.msft-osdu-test.org/api/notification/v1/api-docs
* **api-docs (YAML)** :https://osdu-glab.msft-osdu-test.org/api/notification/v1/api-docs.yaml
## Other Changes
- **Configurable** descriptions managed in [swagger.properties](https://community.opengroup.org/osdu/platform/system/partition/-/blob/az/td-oas/partition-core/src/main/resources/swagger.properties)
- Deleted 'HomeController'
- Marked the 'GlobalErrorController' as 'Hidden' for documentation
- Updated Readme for swagger related information
## References
- https://springdoc.org/faq.html#_can_i_use_spring_property_with_swagger_annotations
- https://springdoc.org/migrating-from-springfox.htmlM18 - Release 0.21Thulasi Dass SubramanianThulasi Dass Subramanianhttps://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/367ReadOnlyRootFileSystem changes for AWS2023-04-06T23:08:47ZAbhay JoshiReadOnlyRootFileSystem changes for AWS## 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?
- [YES/NO]
NO
## Does this introduce a change in the clou...## 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?
- [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?
System can write to AWS service pod
## What is the new/expected behavior?
System cannot write to AWS service pod
## Have you added/updated Unit Tests and Integration Tests?
No
## Any other useful informationM18 - Release 0.21Okoun-Ola Fabien HouetoAbhay JoshiOkoun-Ola Fabien Houetohttps://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/366AWS integration merge2023-04-07T12:44:55ZManish JangidAWS integration merge## 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? AWS pom changes and aws devops changes
## Have you added/updated Unit Tests and Integration Tests? No
## Any other useful informationM18 - Release 0.21https://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/365Draft: Dummy branch to test notification2023-10-11T16:20:00Zsaketh somarajuDraft: Dummy branch to test notificationhttps://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/364Close deleted subscriptions2023-03-30T18:40:33ZAlok JoshiClose deleted subscriptionsToday, the subscription manager in Notification service doesn't close/unregister deleted subscriptions for SB topics. In a scenario when a subscription is deleted, the registered client still attempts to pull messages from the subscripti...Today, the subscription manager in Notification service doesn't close/unregister deleted subscriptions for SB topics. In a scenario when a subscription is deleted, the registered client still attempts to pull messages from the subscription (which doesn't exist now).
This causes an explosion of error logs in the Trace table. The log message looks like this:
`Exception RECEIVE occurred in service bus message in exception phase The messaging entity '<service-bus-resource>:topic:recordstopic~15|<notification-id>' could not be found`
The number of such logs is very very large, they only go away when service is restarted.
This solution closes the connections for which the subscription doesn't exist in the cosmosDbM17 - Release 0.20Alok JoshiChad LeongAlok Joshihttps://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/363changes to fix s360 vulnerabilities2023-03-28T14:08:43ZAbhiram Bondadachanges to fix s360 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?
- NO
## Does this introduce a change in the cloud provide...## 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
- [x] 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 informationhttps://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/362Dummy to check Azure Code coverage dependency2023-10-11T16:19:58ZShreya ShahDummy to check Azure Code coverage dependency## Overview
To check azure code coverage dependency changes were successful or not
## References
https://community.opengroup.org/osdu/platform/ci-cd-pipelines/-/merge_requests/884## Overview
To check azure code coverage dependency changes were successful or not
## References
https://community.opengroup.org/osdu/platform/ci-cd-pipelines/-/merge_requests/884Shreya ShahShreya Shahhttps://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/361Vulnerability fix for IBM2023-03-31T08:22:49ZDevdatta SantraVulnerability fix for IBMVulnerability fix for IBM for `jackson` lib
| CVE-2022-42004 | https://nvd.nist.gov/vuln/detail/CVE-2022-42004 |
|----------------|-------------------------------------------------|
| CVE-2022-42003 | https://nvd.nist.gov/vuln/detail/CV...Vulnerability fix for IBM for `jackson` lib
| CVE-2022-42004 | https://nvd.nist.gov/vuln/detail/CVE-2022-42004 |
|----------------|-------------------------------------------------|
| CVE-2022-42003 | https://nvd.nist.gov/vuln/detail/CVE-2022-42003 |M17 - Release 0.20Devdatta SantraDevdatta Santrahttps://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/360Dummy to check Azure Code coverage dependency2023-04-11T10:17:05ZShreya ShahDummy to check Azure Code coverage dependency##Overview
To check azure code coverage dependency changes were successful or not
##References
https://community.opengroup.org/osdu/platform/ci-cd-pipelines/-/merge_requests/882##Overview
To check azure code coverage dependency changes were successful or not
##References
https://community.opengroup.org/osdu/platform/ci-cd-pipelines/-/merge_requests/882Shreya ShahShreya Shahhttps://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/359[GONRG-6649] Define global vars in notification2023-08-18T15:24:02ZOleksandr Kosse (EPAM)[GONRG-6649] Define global vars in notification## Type of change
- [ ] Bug Fix
- [ ] Feature
- [X] Refactoring
**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 ...## Type of change
- [ ] Bug Fix
- [ ] Feature
- [X] Refactoring
**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?
## What is the new/expected behavior?
## Have you added/updated Unit Tests and Integration Tests?
## Any other useful informationM17 - Release 0.20https://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/358Renaming dependency helm chart repo to osdu-aws and removing versioning const...2023-03-17T19:46:22ZMarc Burnie [AWS]Renaming dependency helm chart repo to osdu-aws and removing versioning constraintsM17 - Release 0.20Marc Burnie [AWS]Marc Burnie [AWS]https://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/357Draft: Vulnerability Fixes For Notification Service2023-04-04T09:43:31ZKamalika SahaDraft: Vulnerability Fixes For Notification Service## 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?
- [ ] AWS
- [x] 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 informationKamalika SahaKamalika Sahahttps://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/356Alternate GC int tests2023-08-18T15:24:03ZKanstantsin Dubrouski [EPAM / GCP]Alternate GC int testsM17 - Release 0.20Riabokon Stanislav(EPAM)[GCP]Riabokon Stanislav(EPAM)[GCP]