Register merge requestshttps://community.opengroup.org/osdu/platform/system/register/-/merge_requests2024-03-19T14:28:48Zhttps://community.opengroup.org/osdu/platform/system/register/-/merge_requests/447spring 6 upgrade2024-03-19T14:28:48ZYunhua Koglinspring 6 upgrade# Merge request template# Merge request templateM23 - Release 0.26Yunhua KoglinYunhua Koglinhttps://community.opengroup.org/osdu/platform/system/register/-/merge_requests/436updated ibm lib version2024-01-09T12:03:29ZNikhil Patilnikhil.patil5@ibm.comupdated ibm lib versionupdated ibm lib versionupdated ibm lib versionM22 - Release 0.25Nikhil Patilnikhil.patil5@ibm.comNikhil Patilnikhil.patil5@ibm.comhttps://community.opengroup.org/osdu/platform/system/register/-/merge_requests/437Merge branch 'ibmlib-version-update' into 'master'2024-01-09T12:03:29ZNikhil Patilnikhil.patil5@ibm.comMerge branch 'ibmlib-version-update' into 'master'Original merge https://community.opengroup.org/osdu/platform/system/register/-/merge_requests/436Original merge https://community.opengroup.org/osdu/platform/system/register/-/merge_requests/436M22 - Release 0.25Nikhil Patilnikhil.patil5@ibm.comNikhil Patilnikhil.patil5@ibm.comhttps://community.opengroup.org/osdu/platform/system/register/-/merge_requests/435Register update ibm lib version2023-12-28T10:15:26ZIsha KumariRegister update ibm lib versionRegister update ibm lib versionRegister update ibm lib versionM22 - Release 0.25Isha KumariIsha Kumarihttps://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/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/425Upgrade os-core-common and Spring dependency versions to address vulnerabilities2023-12-01T17:58:28ZSolomon AyalewUpgrade os-core-common and Spring dependency versions to address vulnerabilities- pull latest version os-core-common
- fix CVE-2023-20863,CVE-2023-20883, CVE-2023-34034 and other org.springframework:spring-core/security vulnerabilitiesge request template- pull latest version os-core-common
- fix CVE-2023-20863,CVE-2023-20883, CVE-2023-34034 and other org.springframework:spring-core/security vulnerabilitiesge request templateM22 - Release 0.25https://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/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/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/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/390netty, guava vulnerability fixes2023-08-25T10:06:24ZRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comnetty, guava vulnerability fixesGuava to 32.0.1-jre
Netty to 4.1.97.FinalGuava to 32.0.1-jre
Netty to 4.1.97.FinalM20 - Release 0.23Rustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comhttps://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 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/31Removed unhardcode repositories and distribution management from all poms (GO...2023-08-18T20:51:45ZRiabokon Stanislav(EPAM)[GCP]Removed unhardcode repositories and distribution management from all poms (GONRG-1059)## Type of change
- [ ] Bug Fix
- [X] Feature
ADR: https://community.opengroup.org/osdu/platform/system/home/-/issues/55
## Does this introduce a change in the core logic?
- [YES]
## Does this introduce a change in the cloud provider...## Type of change
- [ ] Bug Fix
- [X] Feature
ADR: https://community.opengroup.org/osdu/platform/system/home/-/issues/55
## 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 new/expected behavior?
This MR brings changes to POMs (root, azure, gcp) to improve (unhardcode) the way how repositories are being pointed. It now uses set of properties defined in the `.mvn/community-maven.settings.xml`
## Have you added/updated Unit Tests and Integration Tests?
- [YES]
## Any other useful informationM1 - Release 0.1Dmitriy RudkoRostislav Dublin (EPAM)Dmitriy Rudkohttps://community.opengroup.org/osdu/platform/system/register/-/merge_requests/41Skip one test should_beAbleToRunApiInParallel(TestDeleteActionApi) for IBM2023-08-18T20:51:32ZBhushan RadeSkip one test should_beAbleToRunApiInParallel(TestDeleteActionApi) for IBMSkip one test should_beAbleToRunApiInParallel(TestDeleteActionApi)Skip one test should_beAbleToRunApiInParallel(TestDeleteActionApi)M1 - Release 0.1Anuj GuptaAnuj Guptahttps://community.opengroup.org/osdu/platform/system/register/-/merge_requests/59removed Google dependencies from IBM modules2023-08-18T20:51:07ZBhushan Raderemoved Google dependencies from IBM modulesremoved Google dependencies from IBM module
[Issue#25](https://community.opengroup.org/osdu/platform/system/register/-/issues/25)removed Google dependencies from IBM module
[Issue#25](https://community.opengroup.org/osdu/platform/system/register/-/issues/25)M1 - Release 0.1Anuj GuptaAnuj Guptahttps://community.opengroup.org/osdu/platform/system/register/-/merge_requests/65Merging IBM Implementation2023-08-18T20:50:59ZMallikarjuna MallichettuMerging IBM ImplementationMerging IBM ImplementationMerging IBM ImplementationM1 - Release 0.1Anuj GuptaAnuj Guptahttps://community.opengroup.org/osdu/platform/system/register/-/merge_requests/78Switching the dependencies to release versions2023-08-18T20:50:44ZDavid Diederichd.diederich@opengroup.orgSwitching the dependencies to release versionsThis changes the library dependencies to use released versions of the core libraries.
They were previously depending on SNAPSHOT versions, which are less stable versions.
More importantly, the SNAPSHOT versions are periodically purged fr...This changes the library dependencies to use released versions of the core libraries.
They were previously depending on SNAPSHOT versions, which are less stable versions.
More importantly, the SNAPSHOT versions are periodically purged from the system to save disk space -- this happened recently.
Since these libraries no longer exist on community, building becomes difficult.
This MR moves those dependencies to a release version, which is better going forward and allows FOSSA to do the build and get good dependency information.
I assert that there are no substantial changes between the SNAPSHOT version I moved from and the latest release version that I moved to.
It's difficult to know which commit the SNAPSHOT dependency linked to, since it moved many times, but here are the differences from the last time the SNAPSHOT dependency was listed and the one commit that has the release version (0.7.0).
All of these changes were from me, updating versions and references as part of the release process.
- [GCP Differences from v0.6.1-SNAPSHOT to 0.7.0](https://community.opengroup.org/osdu/platform/system/lib/cloud/gcp/os-core-lib-gcp/-/compare/ff52818d929b7a32e491b75743285026c4c0a9b4...v0.7.0)
- [IBM Differences from v0.3.8-SNAPSHOT to 0.7.0](https://community.opengroup.org/osdu/platform/system/lib/cloud/ibm/os-core-lib-ibm/-/compare/42d057eeee8f0299e7f90f1158c24f7fc0187dbc...v0.7.0)
There were code changes between the latest version of v0.3.6-SNAPSHOT and 0.7.0, but they appear to be additions only.
I don't think this will impact compatibility.
- [IBM Differences from v0.3.6-SNAPSHOT to 0.7.0](https://community.opengroup.org/osdu/platform/system/lib/cloud/ibm/os-core-lib-ibm/-/compare/030d7bdb47271193eebfe85515fc83542daa9a55...v0.7.0)
Separately, since I was working with FOSSA, I updated the configuration file and the corresponding NOTICE changes resulting from the new module.M5 - Release 0.8David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/register/-/merge_requests/100Updated version of os-core-lib-ibm to 0.9.02023-08-18T20:50:19ZRitika KaushalUpdated version of os-core-lib-ibm to 0.9.0updated os-core-lib-ibm version to 0.9.0updated os-core-lib-ibm version to 0.9.0M8 - Release 0.11Ritika KaushalRitika Kaushal