Schema merge requestshttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests2022-04-30T20:43:53Zhttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/288fix lib conflicts2022-04-30T20:43:53ZRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comfix lib conflictsM12 - Release 0.15Riabokon Stanislav(EPAM)[GCP]Riabokon Stanislav(EPAM)[GCP]https://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/290Improve object store bucket naming (GONRG-4607)2022-05-05T12:38:19ZRiabokon Stanislav(EPAM)[GCP]Improve object store bucket naming (GONRG-4607)## Type of change
- [ ] Bug Fix
- [x] Feature
## 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] GCP
- [ ] IB...## Type of change
- [ ] Bug Fix
- [x] Feature
## 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] GCP
- [ ] IBM
## Does this introduce a breaking change?
- [YES]
## What is the current behavior?
Bucket name resolving is limited only by the project id present in tenant info:
```
<projectId>-schema
<projectId-system-schema
```
## What is the new/expected behavior?
Bucket name resolving will use not only project id but also a tenant name:
```
<projectId>-<name>-schema
<projectId-<name>-system-schema
```M12 - Release 0.15Riabokon Stanislav(EPAM)[GCP]Riabokon Stanislav(EPAM)[GCP]https://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/299Update pom.xml2022-05-19T15:11:25ZShrikant GargUpdate pom.xmlcore lib updatecore lib updateM12 - Release 0.15Shrikant GargShrikant Garghttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/300Implement int tests for Anthos env (GONRG-4994)2022-05-24T05:21:54ZRiabokon Stanislav(EPAM)[GCP]Implement int tests for Anthos env (GONRG-4994)M12 - Release 0.15Rustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comRiabokon Stanislav(EPAM)[GCP]Rustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comhttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/302update pom.xml2022-05-24T09:50:26ZAshwani Pandeyupdate pom.xmlupdate IBM core lib version to 0.15.0-rc2update IBM core lib version to 0.15.0-rc2M12 - Release 0.15Ashwani PandeyAshwani Pandeyhttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/307Aws patch pyjwt2022-05-27T23:31:35ZMarc Burnie [AWS]Aws patch pyjwtM12 - Release 0.15Marc Burnie [AWS]Marc Burnie [AWS]https://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/319Cherry-pick 'Enable the Published mode for System schema' into release/0.152022-06-16T14:49:50ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Enable the Published mode for System schema' into release/0.15Original MR: !306Original MR: !306M12 - Release 0.15David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/320Upgrade Core IBM Library for Release 0.152022-06-17T14:14:50ZDavid Diederichd.diederich@opengroup.orgUpgrade Core IBM Library for Release 0.15This automated MR upgrades the first party libraries (other OSDU libraries) to utilize the latest release.
The intent is to keep the OSDU projects utilizing the latest available code to ensure widespread usage and stability.
However, any...This automated MR upgrades the first party libraries (other OSDU libraries) to utilize the latest release.
The intent is to keep the OSDU projects utilizing the latest available code to ensure widespread usage and stability.
However, any library that is older than the previous release will be left as-is, since the upgrade is likely to be more complicated.
Furthermore, the upgrade should only be merged in the CI pipeline reports success.
If this MR has failed, we can spend a little time investigating to see if a trivial upgrade could achieve compatiblity to the new library.
But significant upgrade efforts should not occur on this MR, as part of the release tagging process.
Instead, significant work should be scheduled for a subsequent milestone.
### Dependency Information Before the Upgrade
```
Branch: master
SHA: 8a3877d37a2cb230f92ba1e64ff389894c39f55f
Maven: 0.16.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------------------------------------------- | ---------------- | ----------------- |
| core-lib-azure | 0.14.0-rc2 | 0.6.1 |
| core-lib-gcp | 0.15.0-rc3 | |
| os-core-lib-aws | 0.14.0-rc2 | 0.13.0, 0.3.16 |
| obm | 0.15.0-rc5 | |
| oqm | 0.15.0-rc2 | |
| os-core-common | 0.13.0 | 0.13.0 |
| os-core-lib-ibm | 0.15.0-rc2 | 0.15.0-rc3, 0.7.0 |
| osm | 0.15.0-rc5 | |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.13.2.2, 2.11.4 | 2.11.3 |
| (3rd Party) net.minidev.json-smart | 2.4.7 | 2.3 |
| (3rd Party) org.apache.logging.log4j.log4j-api | 2.17.1 | 2.13.3 |
| (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 |
```
Critical: Found Vulnerable Jackson Databind dependency (<2.12.6.1 || >=2.13.0 <2.13.2.1)
```
### Dependency Information After the Upgrade
```
Branch: core-ibm-upgrade
SHA: 230750aeb2ba98446e184d842a0d4d7f53e31ed4
Maven: 0.16.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------------------------------------------- | ---------------- | -------------- |
| core-lib-azure | 0.14.0-rc2 | 0.6.1 |
| core-lib-gcp | 0.15.0-rc3 | |
| os-core-lib-aws | 0.14.0-rc2 | 0.13.0, 0.3.16 |
| obm | 0.15.0-rc5 | |
| oqm | 0.15.0-rc2 | |
| os-core-common | 0.13.0 | 0.13.0 |
| os-core-lib-ibm | 0.15.2 | 0.15.2, 0.7.0 |
| osm | 0.15.0-rc5 | |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.13.2.2, 2.11.4 | 2.11.3 |
| (3rd Party) net.minidev.json-smart | 2.4.7 | 2.3 |
| (3rd Party) org.apache.logging.log4j.log4j-api | 2.17.1 | 2.13.3 |
| (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 |
```
Critical: Found Vulnerable Jackson Databind dependency (<2.12.6.1 || >=2.13.0 <2.13.2.1)
```M12 - Release 0.15https://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/323Cherry-pick 'jackson version update' into release/0.152022-06-17T14:16:39ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'jackson version update' into release/0.15Original MR: !316Original MR: !316M12 - Release 0.15David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/324Cherry-pick 'Enabling Junit execution for core module' into release/0.152022-06-17T14:42:05ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Enabling Junit execution for core module' into release/0.15Original MR: !322Original MR: !322M12 - Release 0.15David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/311Upgrade First Party Library Dependencies for Release 0.152022-06-17T14:43:42ZDavid Diederichd.diederich@opengroup.orgUpgrade First Party Library Dependencies for Release 0.15This automated MR upgrades the first party libraries (other OSDU libraries) to utilize the latest release.
The intent is to keep the OSDU projects utilizing the latest available code to ensure widespread usage and stability.
However, any...This automated MR upgrades the first party libraries (other OSDU libraries) to utilize the latest release.
The intent is to keep the OSDU projects utilizing the latest available code to ensure widespread usage and stability.
However, any library that is older than the previous release will be left as-is, since the upgrade is likely to be more complicated.
Furthermore, the upgrade should only be merged in the CI pipeline reports success.
If this MR has failed, we can spend a little time investigating to see if a trivial upgrade could achieve compatiblity to the new library.
But significant upgrade efforts should not occur on this MR, as part of the release tagging process.
Instead, significant work should be scheduled for a subsequent milestone.
### Dependency Information Before the Upgrade
```
Branch: master
SHA: 8f09057026b1f2e85b38e4191506d0b81457a131
Maven: 0.15.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------------------------------------------- | ---------------- | ----------------- |
| core-lib-azure | 0.14.0-rc2 | 0.6.1 |
| core-lib-gcp | 0.15.0-rc3 | |
| os-core-lib-aws | 0.14.0-rc2 | 0.13.0, 0.3.16 |
| obm | 0.15.0-rc5 | |
| oqm | 0.15.0-rc2 | |
| os-core-common | 0.13.0 | 0.13.0 |
| os-core-lib-ibm | 0.15.0-rc2 | 0.15.0-rc3, 0.7.0 |
| osm | 0.15.0-rc5 | |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.13.2.2, 2.11.4 | 2.11.3 |
| (3rd Party) net.minidev.json-smart | 2.4.7 | 2.3 |
| (3rd Party) org.apache.logging.log4j.log4j-api | 2.17.1 | 2.13.3 |
| (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 |
```
Critical: Found Vulnerable Jackson Databind dependency (<2.12.6.1 || >=2.13.0 <2.13.2.1)
```
### Dependency Information After the Upgrade
```
Branch: dependency-upgrade
SHA: 900e37f519aec3e70d75b31d561df5213fbb2267
Maven: 0.15.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------------------------------------------- | ---------------- | -------------- |
| core-lib-azure | 0.14.0-rc2 | 0.6.1 |
| core-lib-gcp | 0.15.0 | |
| os-core-lib-aws | 0.14.0-rc2 | 0.13.0, 0.3.16 |
| obm | 0.15.0 | |
| oqm | 0.15.0 | |
| os-core-common | 0.13.0 | 0.13.0 |
| os-core-lib-ibm | 0.15.1 | 0.15.1, 0.7.0 |
| osm | 0.15.0 | |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.13.2.2, 2.11.4 | 2.11.3 |
| (3rd Party) net.minidev.json-smart | 2.4.7 | 2.3 |
| (3rd Party) org.apache.logging.log4j.log4j-api | 2.17.1 | 2.13.3 |
| (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 |
```
Critical: Found Vulnerable Jackson Databind dependency (<2.12.6.1 || >=2.13.0 <2.13.2.1)
```M12 - Release 0.15https://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/325Cherry-pick 'Upgrade Core IBM Library for Release 0.15' into release/0.152022-06-20T19:50:54ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Upgrade Core IBM Library for Release 0.15' into release/0.15Original MR: !320Original MR: !320M12 - Release 0.15David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/326Cherry-pick 'Upgrade First Party Library Dependencies for Release 0.15' into ...2022-06-20T19:51:09ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Upgrade First Party Library Dependencies for Release 0.15' into release/0.15Original MR: !311Original MR: !311M12 - Release 0.15David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/327Cherry-pick 'Slb nested ref validation' into release/0.152022-06-20T19:51:18ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Slb nested ref validation' into release/0.15Original MR: !321Original MR: !321M12 - Release 0.15David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/329Cherry-pick 'OSDU-DD-M12-Delivery' into release/0.152022-06-21T16:07:22ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'OSDU-DD-M12-Delivery' into release/0.15Original MR: !301Original MR: !301M12 - Release 0.15David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/328add memory, and adjust heap config2022-06-28T15:29:03ZRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comadd memory, and adjust heap configM13 - Release 0.16Rustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comhttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/336Upgraed log4j2 version to fix vulnerabilitie2022-07-12T11:50:51ZVineeth Guna [Microsoft]Upgraed log4j2 version to fix vulnerabilitieVineeth Guna [Microsoft]Vineeth Guna [Microsoft]https://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/339Update core lib version2022-07-18T05:19:42ZHarsheet ShahUpdate core lib versionHarsheet ShahHarsheet Shahhttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/341Ibm version upgrade2022-08-03T07:29:56ZAshwani PandeyIbm version upgradeupgrade core lib IBM version to '0.16.0-rc1'upgrade core lib IBM version to '0.16.0-rc1'M13 - Release 0.16Ashwani PandeyAshwani Pandeyhttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/347updated schema url to M10 url2022-08-03T08:17:11ZAnkur Rawatupdated schema url to M10 urlUpdated schema URL to older URl in bootstrap scriptUpdated schema URL to older URl in bootstrap scriptAnkur RawatAnkur Rawat