Storage merge requestshttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests2023-01-09T16:52:55Zhttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/595fixing dependency check2023-01-09T16:52:55ZMarc Burnie [AWS]fixing dependency check# Merge request template# Merge request templateM16 - Release 0.19Marc Burnie [AWS]Marc Burnie [AWS]https://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/594temporarily bypass maven dependency check2023-01-09T14:50:37ZMorris Estepatemporarily bypass maven dependency checkM16 - Release 0.19Morris EstepaMorris Estepahttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/593GONRG-5894- gc rename2023-01-12T23:52:49ZAliaksandr Ramanovich (EPAM)GONRG-5894- gc renameGONRG-5894 - google cloud rebrandingGONRG-5894 - google cloud rebrandingM16 - Release 0.19Aliaksandr Ramanovich (EPAM)Aliaksandr Ramanovich (EPAM)https://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/592GONRG-6196: Remove variables that disable using policy2023-01-12T23:52:49ZVolodymyr Pienskoi [EPAM / GCP]GONRG-6196: Remove variables that disable using policyM16 - Release 0.19Volodymyr Pienskoi [EPAM / GCP]Volodymyr Pienskoi [EPAM / GCP]https://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/591fix acl checking on azure CloudStorageImpl for reading version2023-01-12T23:52:48ZYauheni Lesnikaufix acl checking on azure CloudStorageImpl for reading versionISSUE: https://community.opengroup.org/osdu/platform/system/storage/-/issues/158ISSUE: https://community.opengroup.org/osdu/platform/system/storage/-/issues/158M16 - Release 0.19Yauheni LesnikauYauheni Lesnikauhttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/589[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 storage serviceDecrease ISTIO requests and limits for storage serviceM16 - Release 0.19https://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/588Updated core lib for cors2023-02-02T06:59:09ZVineeth Guna [Microsoft]Updated core lib for cors# Merge request template# Merge request templatehttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/587Vulnerability fix ibm storage service2023-03-30T08:07:19ZPintu GuptaVulnerability fix ibm storage serviceFollowing CVE has been fix into this MR :
| cve | link |
|------------------|-------------------------------------------------|
| PRISMA-2022-0239 | https://github.com/square/okhtt...Following CVE has been fix into this MR :
| cve | link |
|------------------|-------------------------------------------------|
| PRISMA-2022-0239 | https://github.com/square/okhttp/issues/6738 |
| CVE-2022-42003 | https://nvd.nist.gov/vuln/detail/CVE-2022-42003 |
| CVE-2022-42004 | https://nvd.nist.gov/vuln/detail/CVE-2022-42004 |
| CVE-2022-25857 | https://nvd.nist.gov/vuln/detail/CVE-2022-25857 |
| CVE-2022-22965 | https://nvd.nist.gov/vuln/detail/CVE-2022-22965 |
| CVE-2022-25647 | https://nvd.nist.gov/vuln/detail/CVE-2022-25647 |
| CVE-2022-42252 | https://nvd.nist.gov/vuln/detail/CVE-2022-42252 |
| CVE-2022-22965 | https://nvd.nist.gov/vuln/detail/CVE-2022-22965 |M16 - Release 0.19Pintu GuptaPintu Guptahttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/586Dependency fixes for Application crash. Removed other csp from pipleine(gitla...2022-12-23T08:39:37ZAnkur RawatDependency fixes for Application crash. Removed other csp from pipleine(gitlab-ci.yaml).Runtime error Fixes.Runtime error Fixes.Ankur RawatAnkur Rawathttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/585Update ORDC local cache to include data partition information2023-01-04T20:33:22ZKelly ZhouUpdate ORDC local cache to include data partition information# Merge request template
Please refer to [issue](https://community.opengroup.org/osdu/platform/system/storage/-/issues/157)# Merge request template
Please refer to [issue](https://community.opengroup.org/osdu/platform/system/storage/-/issues/157)M16 - Release 0.19https://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/584Cherry-pick 'Bug Fix for Azure: update the message to not be sent to recordst...2022-12-16T00:20:54ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Bug Fix for Azure: update the message to not be sent to recordstopic v2 if feature flag is off' into release/0.18**Original MR**: !582
### 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**: !582
### 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/storage/-/pipelines/new?ref=cherry-pick-for-582)M15 - Release 0.18David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/583upd request for storage deploy2023-08-18T22:20:44ZAliaksandr Ramanovich (EPAM)upd request for storage deploydecrease memory requestsdecrease memory requestsM16 - Release 0.19Aliaksandr Ramanovich (EPAM)Aliaksandr Ramanovich (EPAM)https://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/582Bug Fix for Azure: update the message to not be sent to recordstopic v2 if fe...2022-12-15T16:25:28ZMina OtgonboldBug Fix for Azure: update the message to not be sent to recordstopic v2 if feature flag is off## Type of change
- [x] Bug Fix
- [ ] 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
- [x] Azure
- [ ] GCP
- [ ] IB...## Type of change
- [x] Bug Fix
- [ ] 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
- [x] Azure
- [ ] GCP
- [ ] IBM
## Does this introduce a breaking change?
- [NO]
## What is the current behavior?
Azure message bus sends a message to recordstopic-v2
## What is the new/expected behavior?
If the collaboration feature flag is set to false, we do not send any message to recordstopic v2
## Have you added/updated Unit Tests and Integration Tests?
YesM15 - Release 0.18https://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/581Cherry-pick 'Removing the azure message bus message id' into release/0.182022-12-13T22:51:07ZChad LeongCherry-pick 'Removing the azure message bus message id' into release/0.18**Original MR**: !550
### 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**: !550
### 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/storage/-/pipelines/new?ref=cherry-pick-for-550)M15 - Release 0.18David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/580Connection to Redis must be protected by password2022-12-19T12:31:27ZRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comConnection to Redis must be protected by password## Type of change
- [ ] Bug Fix
- [x] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a change in the core logic?
- [NO]
## Does this introduce a change in the cloud provi...## Type of change
- [ ] Bug Fix
- [x] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## 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?
- [NO]
## What is the current behavior?
Redis connection service doesn't allow to use passwords in the GCP module.
## What is the new/expected behavior?
It is possible to configure redies clients with passwords.M16 - Release 0.19Riabokon Stanislav(EPAM)[GCP]Riabokon Stanislav(EPAM)[GCP]https://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/579move conversion json checking from CrsConversionService to the separate class...2022-12-19T15:33:18ZYauheni Lesnikaumove conversion json checking from CrsConversionService to the separate class,...This changes for `/query/records:batch` intended to update the conversion reaction to the records with invalid data structure.
For example, if we face the record with the field which has a type of `JsonObject`, but we expected `JsonArray...This changes for `/query/records:batch` intended to update the conversion reaction to the records with invalid data structure.
For example, if we face the record with the field which has a type of `JsonObject`, but we expected `JsonArray`, now appropriate error status will be appended. We used to ignore such fields before.M16 - Release 0.19Yauheni LesnikauYauheni Lesnikauhttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/578Cherry-pick 'consume latest version of core common library and update the way...2022-12-13T06:09:17ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'consume latest version of core common library and update the way of getting parent records' into release/0.18**Original MR**: !532
### 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**: !532
### 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/storage/-/pipelines/new?ref=cherry-pick-for-532)M15 - Release 0.18David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/577Cherry-pick 'Include collaboration context when pushing to new record changed...2022-12-12T22:43:45ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Include collaboration context when pushing to new record changed topic' into release/0.18**Original MR**: !553
### 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**: !553
### 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/storage/-/pipelines/new?ref=cherry-pick-for-553)M15 - Release 0.18David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/575Cherry-pick 'Update Storage to be Collaboration Context Aware' into release/0.182022-12-09T19:39:22ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Update Storage to be Collaboration Context Aware' into release/0.18**Original MR**: !546
### 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**: !546
### 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/storage/-/pipelines/new?ref=cherry-pick-for-546)M15 - Release 0.18David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/574GONRG-5937: Merge GC Helms to the common one2023-01-12T23:53:23ZVolodymyr Pienskoi [EPAM / GCP]GONRG-5937: Merge GC Helms to the common oneM16 - Release 0.19Volodymyr Pienskoi [EPAM / GCP]Volodymyr Pienskoi [EPAM / GCP]