Schema merge requestshttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests2022-10-17T16:42:44Zhttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/404Cherry-pick 'M14 patch schema repo SHA 9d2306c4db8274b34910d4856d8f8a7ef296de...2022-10-17T16:42:44ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'M14 patch schema repo SHA 9d2306c4db8274b34910d4856d8f8a7ef296de1b (2022-10-12) tag v0.17.1' into release/0.17**Original MR**: !403
### 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**: !403
### 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/schema-service/-/pipelines/new?ref=cherry-pick-for-403)M14 - Release 0.17David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/408update buildspec2022-11-18T23:55:19ZMorris Estepaupdate buildspecupdate buildspecupdate buildspecM15 - Release 0.18Morris EstepaMorris Estepahttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/410M14 Upgrade2022-11-20T11:51:14ZAnkur RawatM14 UpgradeM12 changes into M12M12 changes into M12Ankur RawatAnkur Rawathttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/412Fix spring-boot-maven plugin version2022-11-28T16:59:41ZRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comFix spring-boot-maven plugin versionM15 - Release 0.18Chad LeongChad Leonghttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/411using e-mail from headers instead of using Authorizor2022-11-30T14:17:48ZMarc Burnie [AWS]using e-mail from headers instead of using Authorizorusing e-mail from headers instead of using Authorizor since it does not support other IDP's than Cognitousing e-mail from headers instead of using Authorizor since it does not support other IDP's than CognitoM15 - Release 0.18Marc Burnie [AWS]Marc Burnie [AWS]https://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/407OSDU-DD-Delivery-M15 (v0.18.0)2022-12-02T17:58:29ZThomas Gehrmann [slb]OSDU-DD-Delivery-M15 (v0.18.0)- [x] add new M15 schemas from Data Definitions ([state of the member GitLab when publishing](https://gitlab.opengroup.org/osdu/subcommittees/data-def/work-products/schema/-/tree/486046187e92071750f14ccddd596b8e32e4e04d))
- [x] Address i...- [x] add new M15 schemas from Data Definitions ([state of the member GitLab when publishing](https://gitlab.opengroup.org/osdu/subcommittees/data-def/work-products/schema/-/tree/486046187e92071750f14ccddd596b8e32e4e04d))
- [x] Address issue #115 and update the documentation
Closes #118
Closes #115 (documentation)M15 - Release 0.18Thomas Gehrmann [slb]Thomas Gehrmann [slb]https://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/413Update FOSSA NOTICE2022-12-04T08:36:28ZDavid Diederichd.diederich@opengroup.orgUpdate FOSSA NOTICEThis MR updates the attribution file for the project (also known as the `NOTICE` file).
It is important to keep this up to date to satisfy legal requirements of dependency licenses.
We use FOSSA as the tool to scan for and detect these ...This MR updates the attribution file for the project (also known as the `NOTICE` file).
It is important to keep this up to date to satisfy legal requirements of dependency licenses.
We use FOSSA as the tool to scan for and detect these changes.M15 - Release 0.18https://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/414added changes to enable azure_bootstrap job2022-12-05T22:15:22Zshivani karipeadded changes to enable azure_bootstrap job- made changes to enable the azure test and azure bootstrap jobs
- These were disabled when MR [664](https://community.opengroup.org/osdu/platform/ci-cd-pipelines/-/merge_requests/664/diffs) was merged, and from what I can understand, t...- made changes to enable the azure test and azure bootstrap jobs
- These were disabled when MR [664](https://community.opengroup.org/osdu/platform/ci-cd-pipelines/-/merge_requests/664/diffs) was merged, and from what I can understand, this was missed.M15 - Release 0.18shivani karipeshivani karipehttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/416Cherry-pick 'added changes to enable azure_bootstrap job' into release/0.182022-12-06T13:55:52ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'added changes to enable azure_bootstrap job' into release/0.18**Original MR**: !414
### 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**: !414
### 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/schema-service/-/pipelines/new?ref=cherry-pick-for-414)M15 - Release 0.18David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/417Fixed vulnerabilities2022-12-09T07:16:45ZVineeth Guna [Microsoft]Fixed vulnerabilitieshttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/418Upgrade First Party Library Dependencies for Release 0.182022-12-11T07:40:08ZDavid Diederichd.diederich@opengroup.orgUpgrade First Party Library Dependencies for Release 0.18This 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: 9aa46f38a9ec26381543f1608362c90c94e9d31b
Maven: 0.19.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------------------------------------------- | ---------- | ---------------- |
| core-lib-azure | 0.14.0-rc2 | 0.6.1 |
| core-lib-gcp | 0.16.0 | |
| os-core-lib-aws | 0.17.0 | 0.13.0, 0.3.16 |
| obm | 0.16.0 | |
| oqm | 0.16.0 | |
| os-core-common | 0.13.0 | 0.13.0 |
| os-core-lib-ibm | 0.16.0-rc1 | 0.15.2, 0.7.0 |
| osm | 0.16.0 | |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.13.2.2 | 2.13.2.2, 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 |
| (3rd Party) org.springframework.spring-webflux | 5.3.12 | |
| (3rd Party) org.springframework.spring-webmvc | 5.3.22 | 5.3.22 |
```
Warning: Found Vulnerable Spring WebFlux dependency (<5.2.20 || >=5.3.0 <5.3.18)
└─ _Root_
└─ org.opengroup.osdu.os-schema-azure == 0.19.0-SNAPSHOT
└─ com.azure.spring.azure-spring-boot-starter-active-directory == 3.4.0
└─ org.springframework.boot.spring-boot-starter-webflux == 2.4.12
└─ org.springframework.spring-webflux == 5.3.12
```
### Dependency Information After the Upgrade
```
Branch: dependency-upgrade-2
SHA: 6d3a4cc9fd758c7ab75ebb852a14083402a06704
Maven: 0.19.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------------------------------------------- | ---------- | ---------------- |
| core-lib-azure | 0.14.0-rc2 | 0.6.1 |
| core-lib-gcp | 0.16.0 | |
| os-core-lib-aws | 0.18.0 | 0.13.0, 0.3.16 |
| obm | 0.16.0 | |
| oqm | 0.16.0 | |
| os-core-common | 0.13.0 | 0.13.0 |
| os-core-lib-ibm | 0.16.0-rc1 | 0.15.2, 0.7.0 |
| osm | 0.16.0 | |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.13.2.2 | 2.13.2.2, 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 |
| (3rd Party) org.springframework.spring-webflux | 5.3.12 | |
| (3rd Party) org.springframework.spring-webmvc | 5.3.22 | 5.3.22 |
```
Warning: Found Vulnerable Spring WebFlux dependency (<5.2.20 || >=5.3.0 <5.3.18)
└─ _Root_
└─ org.opengroup.osdu.os-schema-azure == 0.19.0-SNAPSHOT
└─ com.azure.spring.azure-spring-boot-starter-active-directory == 3.4.0
└─ org.springframework.boot.spring-boot-starter-webflux == 2.4.12
└─ org.springframework.spring-webflux == 5.3.12
```M15 - Release 0.18https://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/419Cherry-pick 'Upgrade First Party Library Dependencies for Release 0.18' into ...2022-12-12T09:55:55ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Upgrade First Party Library Dependencies for Release 0.18' into release/0.18**Original MR**: !418
### 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**: !418
### 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/schema-service/-/pipelines/new?ref=cherry-pick-for-418)M15 - Release 0.18David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/426Updated core lib for cors2022-12-29T03:53:36ZVineeth Guna [Microsoft]Updated core lib for corshttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/431temporarily bypass maven dependency check2023-01-07T05:28:05ZMorris Estepatemporarily bypass maven dependency checkM16 - Release 0.19Morris EstepaMorris Estepahttps://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/432fixing dependency check2023-01-09T16:51:25ZMarc Burnie [AWS]fixing dependency checkM16 - Release 0.19Marc Burnie [AWS]Marc Burnie [AWS]https://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/429Added system schemas publishing2023-01-10T14:49:35ZYurii Ruban [EPAM / GCP]Added system schemas publishing# Description:
Added system schemas publishing
# How to test:
1. Check messaging variable in service (expected true)
2. Create schema and system schema using API schema service
3. Check message in RabbitMQ or Pub/Sub. Topic name is s...# Description:
Added system schemas publishing
# How to test:
1. Check messaging variable in service (expected true)
2. Create schema and system schema using API schema service
3. Check message in RabbitMQ or Pub/Sub. Topic name is schema schanged.
# Changes include:
- [ ] New feature (a non-breaking change that adds functionality).
# Changes in:
- [x] GCPM16 - Release 0.19Riabokon Stanislav(EPAM)[GCP]Riabokon Stanislav(EPAM)[GCP]https://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/433Removed audience property (GONRG-6246)2023-01-11T14:32:36ZMykhailo Vinnichuk [EPAM / GCP]Removed audience property (GONRG-6246)M16 - Release 0.19Mykhailo Vinnichuk [EPAM / GCP]Mykhailo Vinnichuk [EPAM / GCP]https://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/424Merge GC helms for schema service2023-01-12T23:53:23ZOleh Miniailov [EPAM / GCP]Merge GC helms for schema serviceM16 - Release 0.19https://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/428[GONRG-6178] Decrease ISTIO requests and limits2023-01-12T23:53:23ZOleksandr Kosse (EPAM)[GONRG-6178] Decrease ISTIO requests and limitsDecrease ISTIO requests and limits for schema serviceDecrease ISTIO requests and limits for schema serviceM16 - Release 0.19https://community.opengroup.org/osdu/platform/system/schema-service/-/merge_requests/442Add missing attributes to schema changed event2023-02-07T23:51:49ZRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comAdd missing attributes to schema changed eventM16 - Release 0.19Rustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.com