Schema merge requestshttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests2022-05-11T21:09:38Zhttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/294Adding CRS, CT schemas2022-05-11T21:09:38ZMarc Burnie [AWS]Adding CRS, CT schemas1. Adding CoordinateReferenceSystem and CoordinateTransformation schema 1.1.0 versions for CRS v3 update.
2. Bumping AWS lib version.1. Adding CoordinateReferenceSystem and CoordinateTransformation schema 1.1.0 versions for CRS v3 update.
2. Bumping AWS lib version.M12 - Release 0.15JoeSpencer Suttonsuttonsp@amazon.comMarc Burnie [AWS]Okoun-Ola Fabien HouetoJoehttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/287Fixed spring context for anthos. Refactoring code.2022-05-01T06:53:24ZRiabokon Stanislav(EPAM)[GCP]Fixed spring context for anthos. Refactoring code.M12 - Release 0.15Riabokon Stanislav(EPAM)[GCP]Riabokon Stanislav(EPAM)[GCP]https://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/264Upgrade First Party Library Dependencies for Release 0.142022-04-05T10:38:44ZDavid Diederichd.diederich@opengroup.orgUpgrade First Party Library Dependencies for Release 0.14This 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: 36b05fad3414ee4a382a0a0000d04b42a1bf8947
Maven: 0.14.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ----------------------------------------------------- | --------------- | -------- |
| core-lib-azure | 0.14.0-rc2 | 0.6.1 |
| core-lib-gcp | 0.14.0-rc2 | |
| os-core-lib-aws | 0.13.0 | 0.3.16 |
| obm | 0.13.1-SNAPSHOT | |
| oqm | 0.13.0-SNAPSHOT | |
| os-core-common | 0.13.0 | 0.13.0 |
| os-core-lib-ibm | 0.13.0 | 0.7.0 |
| osm | 0.13.0-SNAPSHOT | |
| (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 |
### Dependency Information After the Upgrade
```
Branch: dependency-upgrade
SHA: 57f28fec301545aca644bed21b3a001862501233
Maven: 0.14.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ----------------------------------------------------- | ------ | -------- |
| core-lib-azure | 0.14.0 | 0.6.1 |
| core-lib-gcp | 0.14.0 | |
| os-core-lib-aws | 0.14.0 | 0.3.16 |
| obm | 0.14.0 | |
| oqm | 0.14.0 | |
| os-core-common | 0.14.0 | 0.14.0 |
| os-core-lib-ibm | 0.14.0 | 0.7.0 |
| osm | 0.14.0 | |
| (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 |M11 - Release 0.14https://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/188Cherry pick 493aa638 (M9 bootstrap schema)2022-08-23T13:29:51ZAbhishek Kumar (SLB)Cherry pick 493aa638 (M9 bootstrap schema)These schemas are supposed to be bootstrapped with M9These schemas are supposed to be bootstrapped with M9M9 - Release 0.12Thomas Gehrmann [slb]Paresh BehedeThomas Gehrmann [slb]https://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/124Resolve "Correct Internal Versioning" and "Upgrade Core Azure Dependency"2022-01-11T13:23:51ZDavid Diederichd.diederich@opengroup.orgResolve "Correct Internal Versioning" and "Upgrade Core Azure Dependency"Closes #58, #59
See osdu/platform&9 for more details.
## MR's Raison d'être
This MR simultaneously solves the internal versioning of the build, and upgrades the core Azure lib to use the latest release candidate version of the librar...Closes #58, #59
See osdu/platform&9 for more details.
## MR's Raison d'être
This MR simultaneously solves the internal versioning of the build, and upgrades the core Azure lib to use the latest release candidate version of the library. Correcting the internal versioning is an essential first step to all library cleanups -- without it, the testing libraries are permanently locked to the decisions of a very old version of the core libraries. Azure had to be updated at the same time, because it referenced a non-existent version of the library. That would prevent any pipeline from finishing successfully.
*Dependency Table, after the application of this MR's changes*
| Maven Dependencies | _Root POM_ | testing/ |
| ------------------------ | ---------------------- | ----------- |
| os-core-common | 0.9.0, 0.10.0-SNAPSHOT | 0.9.0 |
| core.aws.os-core-lib-aws | 0.9.0 | 0.3.16 |
| core-lib-gcp | 0.9.0 | |
| os-core-lib-ibm | 0.7.0 | 0.7.0 |
| core-lib-azure | 0.10.0-rc10 | 0.10.0-rc10 |
## Housekeeping Updates
### FOSSA Update
This MR also updates the FOSSA attributions, since these need to be kept up to date on every MR. Changes are expected whenever the library dependencies are updated.
### Update Deprecated Pipeline Includes
This MR also updates the `.gitlab-ci.yml` file to use the newer pipeline includes, rather than relying on deprecated includes that mimic old behavior. These housekeeping updates should be done regularly on MRs when they are discovered so the old CI include files can be deleted and no longer supported.
### Testing POM Structure
This MR marks the child modules under `testing/` as child modules. That allows proper detection of the root POMs for this project.M7 - Release 0.10David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/123Draft: Resolve "Upgrade Core Common Dependency"2022-01-11T13:23:50ZDavid Diederichd.diederich@opengroup.orgDraft: Resolve "Upgrade Core Common Dependency"Closes #55
See osdu/platform&9 for more details.
## MR's Raison d'être
This MR updates the core common to use the latest release candidate version of the library. This utilizes newly developed features, and will be upgraded to a full...Closes #55
See osdu/platform&9 for more details.
## MR's Raison d'être
This MR updates the core common to use the latest release candidate version of the library. This utilizes newly developed features, and will be upgraded to a full release during the new release cycle.
*Dependency Table, after the application of this MR's changes*
| Maven Dependencies | _Root POM_ | testing/ |
| ------------------------ | ----------- | ----------- |
| os-core-common | 0.10.0-rc1 | 0.10.0-rc1 |
| core.aws.os-core-lib-aws | 0.9.0 | 0.3.16 |
| core-lib-gcp | 0.9.0 | |
| os-core-lib-ibm | 0.7.0 | 0.7.0 |
| core-lib-azure | 0.10.0-rc10 | 0.10.0-rc10 |
## Housekeeping Updates
### FOSSA Update
This MR also updates the FOSSA attributions, since these need to be kept up to date on every MR. Changes are expected whenever the library dependencies are updated.M7 - Release 0.10David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/646Draft: Trusted gonrg 92062024-03-06T13:02:31ZMykola Ronik [EPAM / GCP]Draft: Trusted gonrg 9206https://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/629Draft: Update Dockerfile2024-01-11T14:22:19ZSiarhei Poliak [EPAM / GCP]Draft: Update Dockerfilehttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/628Draft: Update Dockerfile2024-01-10T08:43:41ZSiarhei Poliak [EPAM / GCP]Draft: Update Dockerfilehttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/625Draft: upgrade json-smart, log4j, reactor-netty2024-01-08T10:50:00ZVidyaDharani LokamDraft: upgrade json-smart, log4j, reactor-netty* upgraded `json-smart` to `2.5.0` to remediate vulnerability.
* upgraded `reactor-netty` to `1.1.14`.
* upgraded `log4j2` to `2.22.0`.
* upgraded `nimbus-jose-jwt-azure` to `9.30.2`.* upgraded `json-smart` to `2.5.0` to remediate vulnerability.
* upgraded `reactor-netty` to `1.1.14`.
* upgraded `log4j2` to `2.22.0`.
* upgraded `nimbus-jose-jwt-azure` to `9.30.2`.https://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/609Draft: Update pom.xml2023-12-06T20:27:31ZVaibhavi KamaniDraft: Update pom.xmlVaibhavi KamaniVaibhavi Kamanihttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/601Draft: Fix vulnerabilities for schema repo2023-11-27T21:22:12ZVaibhavi KamaniDraft: Fix vulnerabilities for schema repoFix vulnerabilities for schema repoFix vulnerabilities for schema repoVaibhavi KamaniVaibhavi Kamanihttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/593Draft: Az/vl test2023-11-15T13:46:13ZVidyaDharani LokamDraft: Az/vl testhttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/592Draft: test2023-11-13T17:40:58ZVidyaDharani LokamDraft: testhttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/590Draft: Az/vl fix preship issue2023-11-10T07:31:50ZVidyaDharani LokamDraft: Az/vl fix preship issuehttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/587Draft: fix 400 statuscode for unknown inputparams2023-11-06T11:22:24ZVidyaDharani LokamDraft: fix 400 statuscode for unknown inputparamshttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/585Draft: return 400-statuscode if getapi contains unknown params or typos2023-11-06T06:27:07ZVidyaDharani LokamDraft: return 400-statuscode if getapi contains unknown params or typosVidyaDharani LokamVidyaDharani Lokamhttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/584Draft: fix to return 400 statuscode when there is a typo or unknown requestparam2023-11-03T06:36:48ZVidyaDharani LokamDraft: fix to return 400 statuscode when there is a typo or unknown requestparamVidyaDharani LokamVidyaDharani Lokamhttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/581Draft: Passing AKS as an environment variable for schema data initialization job2023-10-23T06:53:29ZRitushi ShankerDraft: Passing AKS as an environment variable for schema data initialization job**What is happening :** Currently, during schema data initialization job, the name of the AKS Cluster in which schemas are to be loaded are fetched via az commands.
**What is the fix :** Instead of using az commands, we simply pass the ...**What is happening :** Currently, during schema data initialization job, the name of the AKS Cluster in which schemas are to be loaded are fetched via az commands.
**What is the fix :** Instead of using az commands, we simply pass the correct AKS cluster name as an environment variable to the shell file that loads the schemasRitushi ShankerRitushi Shankerhttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/563Draft: Fetching correct AKS during Schema Data seeding2023-10-20T10:04:13ZRitushi ShankerDraft: Fetching correct AKS during Schema Data seeding**What is happening :** The script responsible for schema data seeding unintentionally fetches the backup AKS cluster as it lists them from the resource group and uses the first value that is being returned.
**What is the fix :** A min...**What is happening :** The script responsible for schema data seeding unintentionally fetches the backup AKS cluster as it lists them from the resource group and uses the first value that is being returned.
**What is the fix :** A minor code change which ensures that the proper AKS cluster is being fetched to load the schemas in it.Ritushi ShankerRitushi Shanker