Storage merge requestshttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests2023-02-17T17:42:57Zhttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/628Cherry-pick 'Generate Swagger using springdoc-openapi' into release/0.192023-02-17T17:42:57ZChad LeongCherry-pick 'Generate Swagger using springdoc-openapi' into release/0.19**Original MR**: !622
### 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**: !622
### 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-622)M16 - Release 0.19David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/626Bypass info and swagger apis in collaboration filter2023-02-17T17:39:10ZAlok JoshiBypass info and swagger apis in collaboration filterCollaborationFilter, when enabled with data partition feature flag strategy, makes a call to Partition service. This call requires data-partition-id header, which is not passed to certain apis (info, swagger, health, etc), thus the api c...CollaborationFilter, when enabled with data partition feature flag strategy, makes a call to Partition service. This call requires data-partition-id header, which is not passed to certain apis (info, swagger, health, etc), thus the api call fails.
We can short-circuit the CollaborationFilter class when url contains one of theseM16 - Release 0.19Alok JoshiAlok Joshihttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/625Security Upgrade AWS2023-03-30T08:07:19ZYash DholakiaSecurity Upgrade AWS# Merge request template# Merge request templateM17 - Release 0.20https://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/624update readme.md2023-02-15T14:54:34ZRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comupdate readme.md# Merge request template# Merge request templateM17 - Release 0.20Rustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comhttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/623GONRG-6470: Update requests according to vpa2023-02-20T11:54:42ZYurii Pelykh [EPAM / GCP]GONRG-6470: Update requests according to vpa- Resources requests updated according to VPA recommendations.- Resources requests updated according to VPA recommendations.M17 - Release 0.20Yurii Pelykh [EPAM / GCP]Yurii Pelykh [EPAM / GCP]https://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/622Generate Swagger using springdoc-openapi2023-03-21T11:34:32ZThulasi Dass SubramanianGenerate Swagger using springdoc-openapi## Type of change
- [ ] Bug Fix
- [x] Feature
**Link to ADR(Architecture Decision Record)** : [Swagger using springdoc-openapi](https://community.opengroup.org/osdu/platform/system/home/-/issues/97)
## OpenAPI 3.0 related changes
- u...## Type of change
- [ ] Bug Fix
- [x] Feature
**Link to ADR(Architecture Decision Record)** : [Swagger using springdoc-openapi](https://community.opengroup.org/osdu/platform/system/home/-/issues/97)
## OpenAPI 3.0 related changes
- upgraded to latest **springdoc openapi** latest version [1.6.14](https://mvnrepository.com/artifact/org.springdoc/springdoc-openapi-ui/1.6.14)
- used [**@OpenAPIDefinition**](https://docs.swagger.io/swagger-core/v2.0.9/apidocs/io/swagger/v3/oas/annotations/OpenAPIDefinition.html) annotation to populate OpenAPI Object fields _[info, tags, servers, security]_
- Documented **Query, Record, Patch , Info & Health** API with OpenAPI 3.0 **Annotations**
- Added the standard HTTP Response(4xx, 5x****x) for API Responses
- Custom Path for
- **Swagger UI**: https://host/context-path/swagger (will redirect to https://host/context-path/swagger-ui/index.html)
- **api-docs (JSON)** : https://host/context-path/api-docs
- **api-docs (YAML)** : https://host/context-path/api-docs.yaml
## Other Changes
- **Configurable** descriptions managed in [swagger.properties](https://community.opengroup.org/osdu/platform/system/storage/-/blob/az/td-swagger-springdoc-openapi/storage-core/src/main/resources/swagger.properties)
- added **Integration Test** cases for _**Swagger-UI, api-docs**_ endpoints
- Hide **deprecated** [**Schema, PubSubEndpoints**] related API operations in documentation
- Deleted HomeController
## References
- https://springdoc.org/faq.html#_can_i_use_spring_property_with_swagger_annotations
- https://springdoc.org/migrating-from-springfox.htmlM16 - Release 0.19Thulasi Dass SubramanianThulasi Dass Subramanianhttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/621Cherry-pick 'Separate out records changed message for collaboration context' ...2023-02-14T07:41:10ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Separate out records changed message for collaboration context' into release/0.19**Original MR**: !607
### 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**: !607
### 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-607)M16 - Release 0.19David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/619Cherry-pick 'adding support for EKS 1.23' into release/0.192023-02-11T01:58:00ZMarc Burnie [AWS]Cherry-pick 'adding support for EKS 1.23' into release/0.19Original MR: https://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/618
Only AWS Helm Chart changesOriginal MR: https://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/618
Only AWS Helm Chart changesM16 - Release 0.19David Diederichd.diederich@opengroup.orgMarc Burnie [AWS]David Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/618Adding support for EKS 1.232023-02-10T21:22:13ZMarc Burnie [AWS]Adding support for EKS 1.23M16 - Release 0.19Marc Burnie [AWS]Marc Burnie [AWS]https://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/617Renaming dependency helm chart repo to osdu-aws and removing versioning const...2023-03-17T19:47:47ZMarc Burnie [AWS]Renaming dependency helm chart repo to osdu-aws and removing versioning constraintsAWS DevOps Changes onlyAWS DevOps Changes onlyM17 - Release 0.20Marc Burnie [AWS]Marc Burnie [AWS]https://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/616GONRG-6443: Remove configmap jobs and variables2023-02-20T11:55:41ZYurii Pelykh [EPAM / GCP]GONRG-6443: Remove configmap jobs and variables- Configmap variable `GC_ENABLE_HELM_CONFIG` removed as unused anymore.- Configmap variable `GC_ENABLE_HELM_CONFIG` removed as unused anymore.M17 - Release 0.20Yurii Pelykh [EPAM / GCP]Yurii Pelykh [EPAM / GCP]https://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/614Fix wrong link2023-02-20T11:54:42ZVladyslav HundarchukFix wrong linkM17 - Release 0.20Vladyslav HundarchukVladyslav Hundarchukhttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/609Azure Update core lib2023-02-02T09:33:23Zharshit aggarwalAzure Update core libTested changes by building, dockerizing and deploying service on test instance
All service integration tests were executed and all succeeded
![image](/uploads/241bc27b6d32a435516de23603ff7d50/image.png)Tested changes by building, dockerizing and deploying service on test instance
All service integration tests were executed and all succeeded
![image](/uploads/241bc27b6d32a435516de23603ff7d50/image.png)harshit aggarwalharshit aggarwalhttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/607Separate out records changed message for collaboration context2023-02-14T12:25:09ZAlok JoshiSeparate out records changed message for collaboration contextEnhancing the implementation of [this ADR](https://community.opengroup.org/osdu/platform/system/storage/-/issues/149#record-changed-on-namespace) by completely separating out message processing mechanism for new records changed topic. We...Enhancing the implementation of [this ADR](https://community.opengroup.org/osdu/platform/system/storage/-/issues/149#record-changed-on-namespace) by completely separating out message processing mechanism for new records changed topic. We've introduced a new model to support the new records changed messages and refactored the shared code so that CSPs that have not implemented the collaboration provider interfaces will keep using the original method (we reverted this back to not include the collaboration context) until they adopt it
The motivation for doing this is to be able to retrieve 'version' and 'modifiedBy' information for message listeners, so we have made a hard separation with a new model and a new publish message interface.
Existing behavior of the system should not be affected with this change.M16 - Release 0.19Alok JoshiAlok Joshihttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/606add owner permission checking to hasViewerAccessToRecord in CloudStorageImpl ...2023-02-20T11:54:42ZYauheni Lesnikauadd owner permission checking to hasViewerAccessToRecord in CloudStorageImpl of Azure CSPadd owner permission checking to hasViewerAccessToRecord in CloudStorageImpl of Azure CSPadd owner permission checking to hasViewerAccessToRecord in CloudStorageImpl of Azure CSPM17 - Release 0.20Yauheni LesnikauYauheni Lesnikauhttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/604GONRG-6337: Remove audience from GC README2023-08-18T22:20:36ZVolodymyr Pienskoi [EPAM / GCP]GONRG-6337: Remove audience from GC READMEM16 - Release 0.19Volodymyr Pienskoi [EPAM / GCP]Volodymyr Pienskoi [EPAM / GCP]https://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/603GC use full image name2023-08-18T22:20:39ZAliaksandr Ramanovich (EPAM)GC use full image nameUse full name for docker imagesUse full name for docker imagesM16 - Release 0.19Aliaksandr Ramanovich (EPAM)Aliaksandr Ramanovich (EPAM)https://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/602GONRG-6319 Data inconsistency handling2023-08-18T22:20:41ZKanstantsin Dubrouski [EPAM / GCP]GONRG-6319 Data inconsistency handlingData inconsistency handlingData inconsistency handlingM16 - Release 0.19Riabokon Stanislav(EPAM)[GCP]Riabokon Stanislav(EPAM)[GCP]https://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/601update collaboration context documentation2023-01-31T17:01:10ZYurii Kondakovupdate collaboration context documentationI updated tutorial documentation (/docs/tutorial folder) regarding collaboration context.I updated tutorial documentation (/docs/tutorial folder) regarding collaboration context.M16 - Release 0.19Yurii KondakovYurii Kondakovhttps://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/600Ibm policy fix2023-01-20T15:31:43ZAshwani PandeyIbm policy fixfixing test case after enabling policyfixing test case after enabling policyM16 - Release 0.19Ashwani PandeyAshwani Pandey