Register merge requestshttps://community.opengroup.org/osdu/platform/system/register/-/merge_requests2022-09-16T08:42:26Zhttps://community.opengroup.org/osdu/platform/system/register/-/merge_requests/105Added new version info endpoint (GONRG-2811)2022-09-16T08:42:26ZDmitrii Novikov (EPAM)Added new version info endpoint (GONRG-2811)## Type of change
- [ ] Bug Fix
- [x] Feature
osdu/platform/system/lib/core/os-core-common#47
## Does this introduce a change in the core logic?
- [YES]
## Does this introduce a change in the cloud provider implementation, if so whic...## Type of change
- [ ] Bug Fix
- [x] Feature
osdu/platform/system/lib/core/os-core-common#47
## 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?
Provides info about maven build and gitM8 - Release 0.11Rostislav Dublin (EPAM)Rostislav Dublin (EPAM)https://community.opengroup.org/osdu/platform/system/register/-/merge_requests/341Aws integration merge2023-05-09T19:53:56ZYash DholakiaAws integration merge# Merge request template# Merge request templateM18 - Release 0.21https://community.opengroup.org/osdu/platform/system/register/-/merge_requests/265Aws integration merge2022-12-02T21:41:43ZMichael SaccoAws integration mergeUpdated `com.google.oauth-client` versions to 1.34.1 and `com.google.code.gson` to 2.8.9Updated `com.google.oauth-client` versions to 1.34.1 and `com.google.code.gson` to 2.8.9M15 - Release 0.18Michael SaccoMichael Saccohttps://community.opengroup.org/osdu/platform/system/register/-/merge_requests/431Cherry-pick 'Full Upgrade of First Party Library Dependencies for Release 0.2...2023-12-16T10:23:24ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Full Upgrade of First Party Library Dependencies for Release 0.25' into release/0.25**Original MR**: !430
### 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**: !430
### 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/register/-/pipelines/new?ref=cherry-pick-for-430)M22 - Release 0.25David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/register/-/merge_requests/416Cherry-pick 'Full Upgrade of First Party Library Dependencies' into release/0.242023-10-19T11:57:42ZChad LeongCherry-pick 'Full Upgrade of First Party Library Dependencies' into release/0.24**Original MR**: !415
### 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**: !415
### 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/register/-/pipelines/new?ref=cherry-pick-for-415)M21 - Release 0.24David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/register/-/merge_requests/412Cherry-pick 'Full Upgrade of First Party Library Dependencies' into release/0.242023-10-17T11:31:09ZSrinivasan NarayananCherry-pick 'Full Upgrade of First Party Library Dependencies' into release/0.24**Original MR**: !397
### 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**: !397
### 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/register/-/pipelines/new?ref=cherry-pick-for-397)M21 - Release 0.24David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/register/-/merge_requests/379Cherry-pick 'Test Cases failure fixes' into release/0.222023-07-26T09:01:16ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Test Cases failure fixes' into release/0.22**Original MR**: !378
### 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**: !378
### 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/register/-/pipelines/new?ref=cherry-pick-for-378)M19 - Release 0.22David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/register/-/merge_requests/381Cherry-pick 'Test Cases failure fixes.' into release/0.222023-07-26T11:21:22ZChad LeongCherry-pick 'Test Cases failure fixes.' into release/0.22**Original MR**: !380
### 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**: !380
### 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/register/-/pipelines/new?ref=cherry-pick-for-380)M19 - Release 0.22David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/register/-/merge_requests/133disabled spring web security2023-08-18T20:49:52ZBhushan Radedisabled spring web security# Merge request template# Merge request templateM10 - Release 0.13Anuj GuptaBhushan RadeAnuj Guptahttps://community.opengroup.org/osdu/platform/system/register/-/merge_requests/238Fixed security issues (GONRG-5616)2022-09-08T11:37:43ZRiabokon Stanislav(EPAM)[GCP]Fixed security issues (GONRG-5616)https://community.opengroup.org/osdu/platform/security-and-compliance/home/-/issues/91https://community.opengroup.org/osdu/platform/security-and-compliance/home/-/issues/91M14 - Release 0.17Riabokon Stanislav(EPAM)[GCP]Riabokon Stanislav(EPAM)[GCP]https://community.opengroup.org/osdu/platform/system/register/-/merge_requests/228fixing naming convention for jackson-databind version2022-09-10T10:47:07ZAshwani Pandeyfixing naming convention for jackson-databind versionfixing naming convention for jackson-databind versionfixing naming convention for jackson-databind versionM14 - Release 0.17Ashwani PandeyAshwani Pandeyhttps://community.opengroup.org/osdu/platform/system/register/-/merge_requests/415Full Upgrade of First Party Library Dependencies2023-10-19T10:04:48ZChad 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: 4e790ce530ef4c829b64f5eb4bd1f0f1a5ba45eb
Maven: 0.25.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------------------------------------------- | ------ | ----------------------------------- |
| core-lib-azure | 0.23.2 | 0.23.2 |
| core-lib-gc | 0.23.1 | 0.23.1 |
| core-test-lib-gcp | | 0.22.0 |
| 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.23.0 | 0.23.0 |
| osm | 0.23.0 | |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.14.2 | 2.15.0-rc1, 2.14.1, 2.13.2.2, 2.9.6 |
| (3rd Party) org.yaml.snakeyaml | 2.0 | 1.30, 2.0 |
### Dependency Information After the Upgrade
```
Branch: dependency-upgrade
SHA: 50f54e88eb597e0a0933810972d39d9e6f9ae87b
Maven: 0.25.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------------------------------------------- | ------ | ----------------------------------- |
| core-lib-azure | 0.24.0 | 0.24.0 |
| core-lib-gc | 0.24.0 | 0.24.0 |
| core-test-lib-gcp | | 0.22.0 |
| os-core-lib-aws | 0.24.0 | 0.24.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.14.2 | 2.15.0-rc1, 2.14.1, 2.13.2.2, 2.9.6 |
| (3rd Party) org.yaml.snakeyaml | 2.0 | 1.30, 2.0 |M21 - Release 0.24https://community.opengroup.org/osdu/platform/system/register/-/merge_requests/397Full Upgrade of First Party Library Dependencies2023-10-17T10:23:36ZChad 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 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.
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: dc20c59225762e9c3bd8311a3b7cbc102ae6e6ed
Maven: 0.24.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------------------------------------------- | ---------- | ----------------------------------- |
| core-lib-azure | 0.20.0-rc5 | 0.13.0 |
| core-lib-gc | 0.21.0 | 0.21.0 |
| core-test-lib-gcp | | 0.21.0 |
| os-core-lib-aws | 0.21.0 | 0.21.0 |
| oqm | 0.21.0 | |
| os-core-common | 0.22.0-rc4 | 0.21.0, 0.13.0 |
| os-core-lib-ibm | 0.21.0 | 0.21.0 |
| osm | 0.21.0 | |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.14.2 | 2.15.0-rc1, 2.14.1, 2.13.2.2, 2.9.6 |
| (3rd Party) org.yaml.snakeyaml | 2.0 | 1.30, 1.33, 2.0 |
### Dependency Information After the Upgrade
```
Branch: dependency-upgrade
SHA: 89f5537dd429b30809906defa76a2cf0d3d687ee
Maven: 0.24.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------------------------------------------- | ------ | ----------------------------------- |
| core-lib-azure | 0.23.2 | 0.23.2 |
| core-lib-gc | 0.23.1 | 0.23.1 |
| core-test-lib-gcp | | 0.22.0 |
| 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.23.0 | 0.23.0 |
| osm | 0.23.0 | |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.14.2 | 2.15.0-rc1, 2.14.1, 2.13.2.2, 2.9.6 |
| (3rd Party) org.yaml.snakeyaml | 2.0 | 1.30, 2.0 |M21 - Release 0.24https://community.opengroup.org/osdu/platform/system/register/-/merge_requests/335Full Upgrade of First Party Library Dependencies for Release 0.202023-04-26T11:33:41ZDavid 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: df0162e65933fa82cdf9092214e6262f1dc94aea
Maven: 0.21.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------------------------------------------- | ---------------------- | ----------------------------------- |
| core-lib-azure | 0.20.0-rc5 | 0.13.0 |
| core-lib-gc | 0.20.0-rc6 | |
| core-lib-gcp | | 0.1.21 |
| core-test-lib-gcp | | 0.0.2 |
| os-core-lib-aws | 0.19.0 | 0.14.0-rc2 |
| obm | 0.20.0-rc2 | |
| oqm | 0.19.0 | |
| os-core-common | 0.19.0, 0.19.0-rc8 | 0.0.18, 0.13.0, 0.15.0 |
| os-core-lib-ibm | 0.16.0-rc1 | 0.15.2 |
| osm | 0.20.0-rc3 | |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.14.2 | 2.15.0-rc1, 2.11.4, 2.13.2.2, 2.9.6 |
| (3rd Party) org.springframework.spring-webmvc | 5.3.26, 5.3.22, 5.3.24 | 5.1.9.RELEASE, 5.3.12 |
| (3rd Party) org.yaml.snakeyaml | 2.0 | 1.23, 1.26, 1.27 |
### Dependency Information After the Upgrade
```
Branch: dependency-upgrade
SHA: 989c88149575b36807335fb0036ec444e8de0b2c
Maven: 0.21.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------------------------------------------- | ------ | ----------------------------------- |
| core-lib-azure | 0.20.0 | 0.20.0 |
| core-lib-gc | 0.20.0 | 0.20.0 |
| core-test-lib-gcp | | 0.20.0 |
| os-core-lib-aws | 0.20.0 | 0.20.0 |
| obm | 0.20.0 | 0.20.0 |
| oqm | 0.20.0 | 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 | 0.20.0 |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.14.2 | 2.15.0-rc1, 2.14.1, 2.13.2.2, 2.9.6 |
| (3rd Party) org.yaml.snakeyaml | 2.0 | 1.30, 2.0 |M18 - Release 0.21Srinivasan NarayananSrinivasan Narayananhttps://community.opengroup.org/osdu/platform/system/register/-/merge_requests/430Full Upgrade of First Party Library Dependencies for Release 0.252023-12-15T20:07:43ZDavid 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
```
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
Branch: master
SHA: 39094f8c79d4c47233965150bf62faa5fd90e58e
Maven: 0.26.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------------------------------------------- | -------------- | ------------------------------------------- |
| core-lib-azure | 0.25.0-rc2 | 0.24.0 |
| core-lib-gc | 0.24.0 | 0.24.0 |
| core-test-lib-gcp | | 0.22.0 |
| os-core-lib-aws | 0.25.0-rc3 | 0.25.0-rc3 |
| oqm | 0.24.0 | |
| os-core-common | 0.25.0-rc2 | 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.14.2, 2.15.2 | 2.15.0-rc1, 2.14.1, 2.13.2.2, 2.9.6, 2.15.2 |
| (3rd Party) org.yaml.snakeyaml | 2.0 | 1.30, 2.0 |
### Dependency Information After the Upgrade
```
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
Branch: dependency-upgrade
SHA: 7bacddd952663dbd3b65001a80a8dff67a3d546d
Maven: 0.26.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------------------------------------------- | -------------- | ------------------------------------------- |
| core-lib-azure | 0.25.0 | 0.25.0 |
| core-lib-gc | 0.25.0 | 0.25.0 |
| core-test-lib-gcp | | 0.22.0 |
| os-core-lib-aws | 0.25.0 | 0.25.0 |
| oqm | 0.25.0 | |
| os-core-common | 0.25.0 | 0.25.0 |
| os-core-lib-ibm | 0.25.0 | 0.25.0 |
| osm | 0.25.0 | |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.14.2, 2.15.2 | 2.15.0-rc1, 2.14.1, 2.13.4.1, 2.9.6, 2.15.2 |
| (3rd Party) org.yaml.snakeyaml | 2.0 | 1.30, 2.0 |M22 - Release 0.25https://community.opengroup.org/osdu/platform/system/register/-/merge_requests/35Ibm cicd test2020-11-04T13:52:45ZAnuj GuptaIbm cicd test# Merge request template# Merge request templateM1 - Release 0.1Anuj GuptaAnuj Guptahttps://community.opengroup.org/osdu/platform/system/register/-/merge_requests/18ibm implementation for Registration2020-09-11T11:20:13ZBhushan Radeibm implementation for Registration# Merge request template
IBM IMPL for Registration service.# Merge request template
IBM IMPL for Registration service.M1 - Release 0.1Alan BrazAlan Brazhttps://community.opengroup.org/osdu/platform/system/register/-/merge_requests/19Ibm Impl for register2020-09-14T14:41:46ZAnuj GuptaIbm Impl for registerIbm Impl for registerIbm Impl for registerM1 - Release 0.1Alan BrazAlan Brazhttps://community.opengroup.org/osdu/platform/system/register/-/merge_requests/22Ibm integration test and code changes into master2023-08-18T20:51:55ZBhushan RadeIbm integration test and code changes into masterThis MR contains changes in the registration-core module - commented default exception handler in GlobalException mapper class and respective unit test.
Reason - int. tests were failing whenever nonexistent tenant passed in an HTTP requ...This MR contains changes in the registration-core module - commented default exception handler in GlobalException mapper class and respective unit test.
Reason - int. tests were failing whenever nonexistent tenant passed in an HTTP request. expected 401, getting 500. TenantInfoFactory class throws AppExcpetion 401 as the tenant does not exist. also, there is one more exception created i.e BeanCreationFactory with a cause - AppException 401. and globaleceptionMapper maps this exception to default Exception mapper which hides the original exception i.e AppExeption 401 and generates 500 error.M1 - Release 0.1Alan BrazAlan Brazhttps://community.opengroup.org/osdu/platform/system/register/-/merge_requests/21IBM Int test code merge2023-08-18T20:51:57ZBhushan RadeIBM Int test code mergeIBM integration test code merge into masterIBM integration test code merge into masterM1 - Release 0.1Alan BrazAlan Braz