Ingestion Workflow merge requestshttps://community.opengroup.org/osdu/platform/data-flow/ingestion/ingestion-workflow/-/merge_requests2023-12-13T15:04:32Zhttps://community.opengroup.org/osdu/platform/data-flow/ingestion/ingestion-workflow/-/merge_requests/503[MSCOSDU-1851] Upgrade core-common, azure and netty2023-12-13T15:04:32ZDeepa Kumari[MSCOSDU-1851] Upgrade core-common, azure and netty1. core-lib-azure: from 0.24.0 to 0.25.0-rc2
1. os-core-common: from 0.24.0 to 0.25.0-rc3
1. org.json: from 20220924 to 20231013
1. netty: from 4.1.98 to 4.1.1011. core-lib-azure: from 0.24.0 to 0.25.0-rc2
1. os-core-common: from 0.24.0 to 0.25.0-rc3
1. org.json: from 20220924 to 20231013
1. netty: from 4.1.98 to 4.1.101M23 - Release 0.26Deepa KumariDeepa Kumarihttps://community.opengroup.org/osdu/platform/data-flow/ingestion/ingestion-workflow/-/merge_requests/136move workflow name validation to core code2023-08-18T11:18:46ZYunhua Koglinmove workflow name validation to core codemove workflow name validation to core codemove workflow name validation to core codeM7 - Release 0.10Yunhua KoglinYunhua Koglinhttps://community.opengroup.org/osdu/platform/data-flow/ingestion/ingestion-workflow/-/merge_requests/208log4j vuln fix2023-08-18T11:17:54ZBhushan Radelog4j vuln fix|module pom changes| Ref Issue|
|------|-----------------------------------------------------------------------------------------------|
| IBM | https://community.opengroup.org/osdu/platform/system/lib/cloud/ibm/os-core-lib-ibm/-/issues...|module pom changes| Ref Issue|
|------|-----------------------------------------------------------------------------------------------|
| IBM | https://community.opengroup.org/osdu/platform/system/lib/cloud/ibm/os-core-lib-ibm/-/issues/2 |
| Core | https://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/issues/54 |
Part of https://community.opengroup.org/osdu/platform/data-flow/ingestion/ingestion-workflow/-/issues/134 seriesM10 - Release 0.13David Diederichd.diederich@opengroup.orgAnuj GuptaBhushan RadeShrikant GargDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/data-flow/ingestion/ingestion-workflow/-/merge_requests/532Java17migration2024-03-27T09:51:53ZVikas Hoode [BP]vikas.hoode@bp.comJava17migrationjdk 17 upgradejdk 17 upgradeM23 - Release 0.26Vikas Hoode [BP]vikas.hoode@bp.comVikas Hoode [BP]vikas.hoode@bp.comhttps://community.opengroup.org/osdu/platform/data-flow/ingestion/ingestion-workflow/-/merge_requests/295jackson version update2022-06-16T04:24:13ZMorris Estepajackson version updatecommit ebf777d2e910366f102664f3613b35addb096dbc
Author: Morris Estepa <estepamo@amazon.com>
Date: 1654889841 -0500
jackson version update.commit ebf777d2e910366f102664f3613b35addb096dbc
Author: Morris Estepa <estepamo@amazon.com>
Date: 1654889841 -0500
jackson version update.M12 - Release 0.15Morris EstepaMorris Estepahttps://community.opengroup.org/osdu/platform/data-flow/ingestion/ingestion-workflow/-/merge_requests/39Implement custom operators api2020-11-24T12:32:37ZVineeth Guna [Microsoft]Implement custom operators apiImplemented all the api's mentioned in the [swagger file](/uploads/4d9bf7606074409eaef6112dac33b408/openapi__1_.yaml) for custom operatorsImplemented all the api's mentioned in the [swagger file](/uploads/4d9bf7606074409eaef6112dac33b408/openapi__1_.yaml) for custom operatorsVineeth Guna [Microsoft]Vineeth Guna [Microsoft]https://community.opengroup.org/osdu/platform/data-flow/ingestion/ingestion-workflow/-/merge_requests/505Implement Airflow facade endpoint2024-01-08T10:10:27ZRiabokon Stanislav(EPAM)[GCP]Implement Airflow facade endpointhttps://community.opengroup.org/osdu/platform/data-flow/ingestion/ingestion-workflow/-/issues/159
# How to test:
Postman and integration tests.
# Changes include:
- [ ] Refactor (a non-breaking change that improves code maintainabilit...https://community.opengroup.org/osdu/platform/data-flow/ingestion/ingestion-workflow/-/issues/159
# How to test:
Postman and integration tests.
# Changes include:
- [ ] Refactor (a non-breaking change that improves code maintainability).
- [ ] Bugfix (a non-breaking change that solves an issue).
- [x] New feature (a non-breaking change that adds functionality).
- [ ] Breaking change (a change that is not backward-compatible and/or changes current functionality).
# Changes in:
- [x] GC
- [x] Azure
- [x] AWS
- [x] IBM
# Dev Checklist:
- [x] Added Unit Tests, wherever applicable.
- [ ] Updated the Readme, if applicable.
- [x] Existing Tests pass
- [x] Verified functionality locally
- [x] Self Reviewed my code for formatting and complex business logic.M23 - Release 0.26Rustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comhttps://community.opengroup.org/osdu/platform/data-flow/ingestion/ingestion-workflow/-/merge_requests/82IBM implementation2023-08-18T11:19:51ZBhushan RadeIBM implementationIBM Changes :
- Added IBM Implementation
Core changes :
- one change in **worflow-core** at /workflow-core/src/main/java/org/opengroup/osdu/workflow/service/**AirflowWorkflowEngineServiceImpl.java**
Issue link for core change - https:...IBM Changes :
- Added IBM Implementation
Core changes :
- one change in **worflow-core** at /workflow-core/src/main/java/org/opengroup/osdu/workflow/service/**AirflowWorkflowEngineServiceImpl.java**
Issue link for core change - https://community.opengroup.org/osdu/platform/data-flow/ingestion/ingestion-workflow/-/issues/87M4 - Release 0.7Anuj GuptaAnuj Guptahttps://community.opengroup.org/osdu/platform/data-flow/ingestion/ingestion-workflow/-/merge_requests/85(GONRG-1608) GCP: Impl audit events2023-08-18T11:19:48ZIgor Filippov (EPAM)(GONRG-1608) GCP: Impl audit events## Type of change
- [ ] Bug Fix
- [X] Feature
## Does this introduce a change in the core logic?
- [YES]
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [ ] Azure
- [ ] GCP
- [ ] I...## Type of change
- [ ] Bug Fix
- [X] Feature
## Does this introduce a change in the core logic?
- [YES]
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [ ] Azure
- [ ] GCP
- [ ] IBM
## Does this introduce a breaking change?
- [NO]
## What is the current behavior?
Audit events doesn't implement
## What is the new/expected behavior?
Audit events implements
## Have you added/updated Unit Tests and Integration Tests?
- [YES]M4 - Release 0.7Dmitriy RudkoRostislav Dublin (EPAM)Dmitriy Rudkohttps://community.opengroup.org/osdu/platform/data-flow/ingestion/ingestion-workflow/-/merge_requests/234Getting workflow status periodically returns 500 error because of an unknown ...2022-07-26T15:08:22ZAnastasiia GelmutGetting workflow status periodically returns 500 error because of an unknown state (GONRG-4248)## Type of change
- [x] Bug Fix
- [ ] Feature
https://community.opengroup.org/osdu/platform/data-flow/ingestion/ingestion-workflow/-/issues/140
---
## Does this introduce a change in the core logic?
- [YES]
## Does this introduce a c...## Type of change
- [x] Bug Fix
- [ ] Feature
https://community.opengroup.org/osdu/platform/data-flow/ingestion/ingestion-workflow/-/issues/140
---
## 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?
- [NO]
## What is the new/expected behavior?
Added new DagState.
https://airflow.apache.org/docs/apache-airflow/stable/stable-rest-api-ref.html#operation/post_dag_run
## Have you added/updated Unit Tests and Integration Tests?
noM11 - Release 0.14Riabokon Stanislav(EPAM)[GCP]Andrei Dalhikh [EPAM/GC]Riabokon Stanislav(EPAM)[GCP]https://community.opengroup.org/osdu/platform/data-flow/ingestion/ingestion-workflow/-/merge_requests/111Getting 500 internal server error when try to retrieve to workflow status (GO...2023-08-18T11:19:08ZRiabokon Stanislav(EPAM)[GCP]Getting 500 internal server error when try to retrieve to workflow status (GONRG-2273)# Description:
GET request does not contain a body. Thus, we got 500 internal server error when try to retrieve to workflow status.
Original issue: https://gitlab.opengroup.org/osdu/subcommittees/ea/projects/pre-shipping/home/-/issues/1...# Description:
GET request does not contain a body. Thus, we got 500 internal server error when try to retrieve to workflow status.
Original issue: https://gitlab.opengroup.org/osdu/subcommittees/ea/projects/pre-shipping/home/-/issues/164
# How to test:
Trigger the workflow POST https://workflow-drgfbg5txq-uc.a.run.app/v1/workflow/Osdu_ingest/workflowRun
Retrieve the status of the workflow GET [https://workflow-drgfbg5txq-uc.a.run.app/v1/workflow/Osdu_ingest/workflowRun/{{runid}}](https://workflow-drgfbg5txq-uc.a.run.app/v1/workflow/Osdu_ingest/workflowRun/%7B%7Brunid%7D%7D)
# Changes include:
- [ ] Refactor (a non-breaking change that improves code maintainability).
- [ ] Bugfix (a non-breaking change that solves an issue).
- [ ] New feature (a non-breaking change that adds functionality).
- [x] Breaking change (a change that is not backward-compatible and/or changes current functionality).
# Changes in:
- [x] GCP
- [x] Azure
- [x] AWS
- [x] IBM
- [x] Common code
# Dev Checklist:
- [ ] Added Unit Tests, wherever applicable.
- [ ] Updated the Readme, if applicable.
- [ ] Existing Tests pass
- [x] Verified functionality locally
- [x] Self Reviewed my code for formatting and complex business logic.
# Other comments:M5 - Release 0.8Rostislav Dublin (EPAM)Rostislav Dublin (EPAM)https://community.opengroup.org/osdu/platform/data-flow/ingestion/ingestion-workflow/-/merge_requests/90Get all workflows tenant2023-08-18T11:19:41ZMayank Saggar [Microsoft]Get all workflows tenantAdded a new workflow api with UTs and ITs.
Get All Workflows starting with *prefix* API with rest end point : */workflow/?prefix="test"*
1 Parameters can be specified for this get request namely: *prefix*.
Queries the database for all...Added a new workflow api with UTs and ITs.
Get All Workflows starting with *prefix* API with rest end point : */workflow/?prefix="test"*
1 Parameters can be specified for this get request namely: *prefix*.
Queries the database for all the workflows having the specified prefix. The resulting items are sorted by timestamp in descending order.
ITs for the api:
* Success cases when:
* prefix is provided
* Unauthorized case with no access token and no data access token.
* Unauthorized when given invalid partition idM4 - Release 0.7https://community.opengroup.org/osdu/platform/data-flow/ingestion/ingestion-workflow/-/merge_requests/504Full Upgrade of First Party Library Dependencies for Release 0.252023-12-15T20:09:01ZDavid Diederichd.diederich@opengroup.orgFull Upgrade of First Party Library Dependencies for Release 0.25This 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: 5d7181d2567c65708bba59cc912dabbabd46f0ae
Maven: 0.26.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------------------------------------------- | -------------------------- | --------------------- |
| core-lib-azure | 0.24.0 | 0.0.28 |
| core-lib-gc | 0.24.0 | |
| os-core-lib-aws | 0.23.0 | 0.23.0 |
| oqm | 0.24.0 | |
| os-core-common | 0.24.0 | 0.24.0, 0.23.0 |
| os-core-lib-ibm | 0.24.0 | 0.24.0 |
| osm | 0.24.0 | |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.13.5, 2.13.2.2, 2.13.4.2 | 2.13.2.2, 2.10.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.springframework.spring-webmvc | 5.3.28, 5.3.24, 5.3.22 | 5.2.2.RELEASE, 5.3.22 |
| (3rd Party) org.yaml.snakeyaml | 2.0 | 1.25, 1.30 |
### Dependency Information After the Upgrade
```
Branch: dependency-upgrade
SHA: 9a416eb3e8df24830cc9232b808d27e6048524ae
Maven: 0.26.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------------------------------------------- | -------------------------- | --------------------- |
| core-lib-azure | 0.25.0 | 0.0.28 |
| core-lib-gc | 0.25.0 | |
| os-core-lib-aws | 0.23.0 | 0.23.0 |
| oqm | 0.25.0 | |
| os-core-common | 0.25.0 | 0.25.0, 0.23.0 |
| os-core-lib-ibm | 0.25.0 | 0.25.0 |
| osm | 0.25.0 | |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.13.5, 2.13.2.2, 2.13.4.2 | 2.13.2.2, 2.10.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.springframework.spring-webmvc | 5.3.28, 5.3.24, 5.3.22 | 5.2.2.RELEASE, 5.3.30 |
| (3rd Party) org.yaml.snakeyaml | 2.0 | 1.25, 1.30 |M22 - Release 0.25https://community.opengroup.org/osdu/platform/data-flow/ingestion/ingestion-workflow/-/merge_requests/489Full Upgrade of First Party Library Dependencies2023-10-20T12:15:40ZChad LeongFull Upgrade of First Party Library DependenciesThis generated MR upgrades the first party libraries (other OSDU libraries) to utilize the latest release.
The intent is to keep all dependent libraries up to date.
This upgrade can be merged immediately without further approval if the C...This generated MR upgrades the first party libraries (other OSDU libraries) to utilize the latest release.
The intent is to keep all dependent libraries up to date.
This upgrade can be merged immediately without further approval if the CI pipeline reports success.
If this MR has failed, we need to work with the maintainers and affected provider teams to find a solution.
### Dependency Information Before the Upgrade
```
Branch: master
SHA: 8848dd0cbbd228abecc2722c9e90c51bef3157c4
Maven: 0.25.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------------------------------------------- | -------------------------- | --------------------- |
| core-lib-azure | 0.23.2 | 0.0.28 |
| core-lib-gc | 0.23.1 | |
| os-core-lib-aws | 0.23.0 | 0.23.0 |
| oqm | 0.23.0 | |
| os-core-common | 0.23.3 | 0.23.3, 0.23.0 |
| os-core-lib-ibm | 0.24.0 | 0.23.0 |
| osm | 0.23.0 | |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.13.5, 2.13.2.2, 2.13.4.2 | 2.13.2.2, 2.10.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.springframework.spring-webmvc | 5.3.28, 5.3.24, 5.3.22 | 5.2.2.RELEASE, 5.3.22 |
| (3rd Party) org.yaml.snakeyaml | 2.0 | 1.25, 1.30 |
### Dependency Information After the Upgrade
```
Branch: dependency-upgrade-2
SHA: 622bf2980eba9c993c098037d03fa2c5ba02e674
Maven: 0.25.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------------------------------------------- | -------------------------- | --------------------- |
| core-lib-azure | 0.24.0 | 0.0.28 |
| core-lib-gc | 0.24.0 | |
| os-core-lib-aws | 0.23.0 | 0.23.0 |
| oqm | 0.24.0 | |
| os-core-common | 0.24.0 | 0.24.0 |
| os-core-lib-ibm | 0.24.0 | 0.24.0 |
| osm | 0.24.0 | |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.13.5, 2.13.2.2, 2.13.4.2 | 2.13.2.2, 2.10.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.springframework.spring-webmvc | 5.3.28, 5.3.24, 5.3.22 | 5.2.2.RELEASE, 5.3.22 |
| (3rd Party) org.yaml.snakeyaml | 2.0 | 1.25, 1.30 |M21 - Release 0.24https://community.opengroup.org/osdu/platform/data-flow/ingestion/ingestion-workflow/-/merge_requests/212Fix log4j (GONRG-4016)2021-12-21T03:36:41ZArtem Dobrynin (EPAM)Fix log4j (GONRG-4016)Updated version to 2.17.0 to fix vulnerabilities
https://community.opengroup.org/groups/osdu/platform/-/epics/11
Part of the #135 seriesUpdated version to 2.17.0 to fix vulnerabilities
https://community.opengroup.org/groups/osdu/platform/-/epics/11
Part of the #135 seriesM10 - Release 0.13Riabokon Stanislav(EPAM)[GCP]Riabokon Stanislav(EPAM)[GCP]https://community.opengroup.org/osdu/platform/data-flow/ingestion/ingestion-workflow/-/merge_requests/92Fixed issues in getworkflowRuns API2023-08-18T11:19:37ZKishore BattulaFixed issues in getworkflowRuns APIChecking existence of workflow when getting workflow runsChecking existence of workflow when getting workflow runsM4 - Release 0.7https://community.opengroup.org/osdu/platform/data-flow/ingestion/ingestion-workflow/-/merge_requests/89Fixed issues in delete workflow API2023-08-18T11:19:43ZKishore BattulaFixed issues in delete workflow APIAzure implementation has a flow to deploy the DAG through workflow service. When delete a workflow we should only delete the DAGs that are registered through workflow service. Sending a flag to decide whether to delete a DAG from airflow...Azure implementation has a flow to deploy the DAG through workflow service. When delete a workflow we should only delete the DAGs that are registered through workflow service. Sending a flag to decide whether to delete a DAG from airflow or not.
It has core changes but default to false for isDeployedThroughWorkflowService as other CSPs haven't implemented this feature.M4 - Release 0.7https://community.opengroup.org/osdu/platform/data-flow/ingestion/ingestion-workflow/-/merge_requests/124Fixed issue in swagger input parameter by upgrading Swagger 2 to Swagger 32021-06-22T12:28:26ZAbhiman NeelakanteswaraFixed issue in swagger input parameter by upgrading Swagger 2 to Swagger 3## Motivation
A bug was raised mentioned that the input parameters in the `params` field for the GET /{workflow_name}/workflowRun API were not accepted. The API did not work from the swagger page but however, worked with Postman.
## C...## Motivation
A bug was raised mentioned that the input parameters in the `params` field for the GET /{workflow_name}/workflowRun API were not accepted. The API did not work from the swagger page but however, worked with Postman.
## Changes
The issue was Swagger 2 was unable to serialize parameters from JSON input to a GET API. This feature is only supported in Open API Spec(OAS)>3.0. Hence, the springfox-swagger version has been updated to 3.0.0
## Known Issues
Recommended library for OAS 3.0 is springdoc-openapi-ui. However, the latest version of this library has an inline script in the index.html of the OAS page. This is currently not allowed according to the security policy in our azure deployment.M7 - Release 0.10Abhiman NeelakanteswaraAbhiman Neelakanteswarahttps://community.opengroup.org/osdu/platform/data-flow/ingestion/ingestion-workflow/-/merge_requests/157Fixed get workflow status request by workflowName (GONRG-3007)2021-10-12T09:29:02ZDmitrii Novikov (EPAM)Fixed get workflow status request by workflowName (GONRG-3007)## Type of change
- [x] Bug Fix
- [ ] Feature
issue: https://community.opengroup.org/osdu/platform/data-flow/ingestion/ingestion-workflow/-/issues/129
## Does this introduce a change in the core logic?
- [YES]
## Does this introduce a...## Type of change
- [x] Bug Fix
- [ ] Feature
issue: https://community.opengroup.org/osdu/platform/data-flow/ingestion/ingestion-workflow/-/issues/129
## 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]
## What is the current behavior?
GET "/{workflow_name}/workflowRun/{runId}" request used 'dagName' instead of 'workflowName' underhood during airflow call.
In case of different 'dagName' and 'workflowName' it leads error:
```
{
"code": 404,
"reason": "Failed to send request.",
"message": "Unable to send request to Airflow. 404 NOT FOUND_{\"error\":\"Dag id workflow_name not found in DagModel\"}_"
}
```
So, 'dagName' parameter was replaced with 'workflowName' in airflow request in `workflow-core/src/main/java/org/opengroup/osdu/workflow/service/AirflowWorkflowEngineServiceImpl.java`
According to the airflow docs there should be dagName
https://airflow.apache.org/docs/apache-airflow/stable/stable-rest-api-ref.html#operation/get_dag_run
or
https://airflow.apache.org/docs/apache-airflow/stable/deprecated-rest-api-ref.htmlM9 - Release 0.12Rostislav Dublin (EPAM)Rostislav Dublin (EPAM)https://community.opengroup.org/osdu/platform/data-flow/ingestion/ingestion-workflow/-/merge_requests/455[Dependency Updates] WhiteSource fixes [jul2023]2023-07-13T09:26:49ZMaksim Malkov[Dependency Updates] WhiteSource fixes [jul2023]### Version updates
[root-pom]
* json-smart -> 2.4.11
* netty-all -> 4.1.72.Final
* netty-handler -> 4.1.72.Final
* netty-codec -> 4.1.68.Final
* netty-common -> 4.1.71.Final
* jersey-client -> 1.19.4
* jackson-core -> 2.13.2
* jackson-...### Version updates
[root-pom]
* json-smart -> 2.4.11
* netty-all -> 4.1.72.Final
* netty-handler -> 4.1.72.Final
* netty-codec -> 4.1.68.Final
* netty-common -> 4.1.71.Final
* jersey-client -> 1.19.4
* jackson-core -> 2.13.2
* jackson-annotations -> 2.13.2
* jackson-databind -> 2.13.5
* guava -> 32.1.1-jre
* snakeyaml -> 2.0
* spring-security-web -> 5.7.8
* tomcat-embed-core -> 9.0.76
* spring-beans -> 5.3.28
* spring-core -> 5.3.28
* spring-context -> 5.3.28
* spring-expression -> 5.3.28
* spring-web -> 5.3.28
* spring-webmvc -> 5.3.28
* tomcat-coyote -> 9.0.76
* json -> 20230618
[azure]
* tomcat-coyote -> 9.0.76M19 - Release 0.22Maksim MalkovMaksim Malkov