Schema merge requestshttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests2024-03-06T13:02:31Zhttps://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/640Draft: Refactor to address sonar issues2024-02-29T18:58:52ZSolomon AyalewDraft: Refactor to address sonar issuesAddress Cognitive and Cyclomatic complexity to bring the project to the acceptable thresholdAddress Cognitive and Cyclomatic complexity to bring the project to the acceptable thresholdM23 - Release 0.26https://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/630Draft: GONRG-9043: update docker image2024-01-10T17:12:52ZYauheni Rykhter (EPAM)Draft: GONRG-9043: update docker imageM23 - Release 0.26Yauheni Rykhter (EPAM)Yauheni Rykhter (EPAM)https://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/624Feature/version upgrade2024-01-09T10:30:15ZAshwani PandeyFeature/version upgradecore-lib-ibm version upgrade to 0.25.1core-lib-ibm version upgrade to 0.25.1M22 - Release 0.25Ashwani PandeyAshwani Pandeyhttps://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/623Schema updated ibm lib version2023-12-28T10:12:25ZIsha KumariSchema updated ibm lib versionSchema updated ibm lib versionSchema updated ibm lib versionM22 - Release 0.25Isha KumariIsha Kumarihttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/619Draft: Bootstrap issue fix2023-12-22T08:51:36ZIsha KumariDraft: Bootstrap issue fixBootstrap issue fixBootstrap issue fixM22 - Release 0.25Isha KumariIsha Kumarihttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/491Fixed library versions to remove vulnerabilities2023-12-08T15:21:46ZVineeth Guna [Microsoft]Fixed library versions to remove vulnerabilitieshttps://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/597fix content-type as application/json in system-schema api2023-11-16T12:11:55ZVidyaDharani Lokamfix content-type as application/json in system-schema api
* As discussed in the above issue received a response with 'application/json' Content-Type, but it is not declared in the schema for system-schema api.
* In this MR we defined the content-type as 'application/json' in system-schema api ...
* As discussed in the above issue received a response with 'application/json' Content-Type, but it is not declared in the schema for system-schema api.
* In this MR we defined the content-type as 'application/json' in system-schema api for the respective api response.M22 - Release 0.25VidyaDharani LokamVidyaDharani Lokamhttps://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 Shanker