OS Core Lib Azure merge requestshttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests2022-09-16T07:34:21Zhttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/243Merge branch 'users/nikhil/fixSBpublishing' into 'master'2022-09-16T07:34:21ZDavid Diederichd.diederich@opengroup.orgMerge branch 'users/nikhil/fixSBpublishing' into 'master'Original MR: !221Original MR: !221M13 - Release 0.16David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/239Cherry-pick 'Replaced insert bulk operation with upsert for cosmos client' in...2022-12-22T18:58:01ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Replaced insert bulk operation with upsert for cosmos client' into release/0.16Original MR: !237Original MR: !237M13 - Release 0.16David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/237Replaced insert bulk operation with upsert for cosmos client2022-09-01T16:14:59ZDmitrii Novikov (EPAM)Replaced insert bulk operation with upsert for cosmos clientReplaced type of operation from insert to replace due to breaking changes in following MRs:
https://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/427
https://community.opengroup.org/osdu/platform/system/lib/cloud/...Replaced type of operation from insert to replace due to breaking changes in following MRs:
https://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/427
https://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/211M13 - Release 0.16Dmitrii Novikov (EPAM)Dmitrii Novikov (EPAM)https://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/226Cherry-pick 'Updated spring boot version' into release/0.162022-12-22T18:58:02ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Updated spring boot version' into release/0.16Original MR: !222Original MR: !222M13 - Release 0.16David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/225Cherry-pick ' Upgrade First Part Library Dependencies for Release 0.16 ' into...2022-12-22T18:58:01ZDavid Diederichd.diederich@opengroup.orgCherry-pick ' Upgrade First Part Library Dependencies for Release 0.16 ' into release/0.16Original MR: !224Original MR: !224M13 - Release 0.16David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/224Upgrade First Part Library Dependencies for Release 0.162022-08-05T07:40:11ZDavid Diederichd.diederich@opengroup.orgUpgrade First Part Library Dependencies for Release 0.16This 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: 20f7e3c9fd85301a83724eda0669c1224cc6a1b8
Maven: 0.17.0-SNAPSHOT
```
| Maven Dependencies | _Root_ |
| ------------------------------------------------------- | -------- |
| os-core-common | 0.15.0 |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.13.2.2 |
### Dependency Information After the Upgrade
```
Branch: dependency-upgrade
SHA: 8f722fd7bde8fbe00aaf97ab3a09260234bfc649
Maven: 0.17.0-SNAPSHOT
```
| Maven Dependencies | _Root_ |
| ------------------------------------------------------- | -------- |
| os-core-common | 0.16.0 |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.13.2.2 |M13 - Release 0.16https://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/222Updated spring boot version2022-09-15T09:46:06ZDmitrii Novikov (EPAM)Updated spring boot versionhttps://community.opengroup.org/osdu/platform/system/indexer-service/-/issues/56
- Updated spring-boot version 2.4.12 -> 2.7.2, lombok version 1.18.16 -> 1.18.24
- Fixed issue with deprecated actuator classeshttps://community.opengroup.org/osdu/platform/system/indexer-service/-/issues/56
- Updated spring-boot version 2.4.12 -> 2.7.2, lombok version 1.18.16 -> 1.18.24
- Fixed issue with deprecated actuator classesM13 - Release 0.16https://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/218Harsheet pvt link validation2023-08-18T12:42:59ZHarsheet ShahHarsheet pvt link validation## All Submissions:
-------------------------------------
* [YES/NO] I have added an explanation of what changes in this merge do and why we should include it?
* [YES/NO] I have updated the documentation accordingly.
* [YES/NO/NA] I have...## All Submissions:
-------------------------------------
* [YES/NO] I have added an explanation of what changes in this merge do and why we should include it?
* [YES/NO] I have updated the documentation accordingly.
* [YES/NO/NA] I have added tests to cover my changes.
* [YES/NO/NA] All new and existing tests passed.
* [YES/NO/NA] My code follows the code style of this project.
* [YES/NO/NA] I ran lint checks locally prior to submission.
## What is the issue or story related to the change?
-------------------------------------
<!-- Please describe the current behavior that you are modifying, 'or' link to a relevant issue.
Feel free to add references to any design documents you might have shared with the team or any
related MR that you are building on top of. -->
High level design:
Issue: <!-- Link any __GitLab__ workitem(s) to this pull request. -->
<!-- Please add implementation details of current set of changes and how the code changes are
doing what they are expected to do. Are there any complex loops or designated code blocks that
should be elaborated? Is there some contextual knowledge that the reviewer should be aware of? -->
Change details:
## Test coverage:
------------------
<!-- Mention unit test coverage of changes. -->
## Does this introduce a breaking change?
-------------------------------------
- [YES/NO]
<!-- If this introduces a breaking change, please describe the impact and migration path for existing applications below. -->
## Pending items
----------------
<!-- Are there changes that you'll introduce in upcoming MRs and hence did not add in this one? Next steps of your
feature can also be mentioned here. -->
## Reviewer request
-------------------
- Please provide an ETA when you plan to review this MR. Write a comment to decline or provide an ETA.
- Block the MR if you feel there is less testing or no details in the MR
- Please cover the following aspects in the MR
-- Coding design: _\<Reviewer1>_
-- Backward Compatibility: _\<Reviewer2>_
-- Feature Logic: _\<Logic design\>_
-- _\<Any other context mention here>_
OR
-- _\<Component 1>_: _\<Reviewer1>_
-- _\<CosmosDB>_: _\<Reviewer2>_
-- _\<ServiceBus>_ _\<Reviewer3>_
-- _\<Mention any other component and owner>_
## Other information
-------------------------------------
<!-- Any other information that is important to this MR such as screenshots of how the component looks before and after the change. -->M13 - Release 0.16Harsheet ShahHarsheet Shahhttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/216Undelete blob2023-07-13T03:28:14ZAlok JoshiUndelete blobAdding `undelete` operation support in the library to enable restoring soft-deleted blobs
We have seen a few records that end up in an inconsistent state where the latest version from CosmosDb for a record is soft-deleted from Blob stor...Adding `undelete` operation support in the library to enable restoring soft-deleted blobs
We have seen a few records that end up in an inconsistent state where the latest version from CosmosDb for a record is soft-deleted from Blob storage. This will fail apis like GET `/api/storage/v2/records/<id>` and POST `/api/storage/v2/query/records:batch`. Restoring the soft delete version from Blob Storage (which is available in CosmosDb metadata for the record) will fix the inconsistency.
Reference docs:
https://docs.microsoft.com/en-us/azure/storage/blobs/soft-delete-blob-manage?tabs=dotnet#restore-soft-deleted-blobs-when-versioning-is-enabled
https://github.com/Azure/azure-sdk-for-java/issues/25943
There will be a follow up change in Storage serviceM13 - Release 0.16Alok JoshiAlok Joshihttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/212Adding validation for private links2023-08-18T12:43:03ZHarsheet ShahAdding validation for private links## All Submissions:
-------------------------------------
* [YES/NO] I have added an explanation of what changes in this merge do and why we should include it? Yes
* [YES/NO] I have updated the documentation accordingly. Yes
* [YES/NO/NA...## All Submissions:
-------------------------------------
* [YES/NO] I have added an explanation of what changes in this merge do and why we should include it? Yes
* [YES/NO] I have updated the documentation accordingly. Yes
* [YES/NO/NA] I have added tests to cover my changes. Yes
* [YES/NO/NA] All new and existing tests passed. Yes
* [YES/NO/NA] My code follows the code style of this project. Yes
* [YES/NO/NA] I ran lint checks locally prior to submission. Yes
## What is the issue or story related to the change?
-------------------------------------
<!-- Please describe the current behavior that you are modifying, 'or' link to a relevant issue.
Feel free to add references to any design documents you might have shared with the team or any
related MR that you are building on top of. -->
Validation for private links
High level design:
Issue: <!-- Link any __GitLab__ workitem(s) to this pull request. -->
<!-- Please add implementation details of current set of changes and how the code changes are
doing what they are expected to do. Are there any complex loops or designated code blocks that
should be elaborated? Is there some contextual knowledge that the reviewer should be aware of? -->
Change details:
## Test coverage:
------------------
<!-- Mention unit test coverage of changes. -->
## Does this introduce a breaking change?
-------------------------------------
- [YES/NO] Yes
<!-- If this introduces a breaking change, please describe the impact and migration path for existing applications below. -->
## Pending items
----------------
<!-- Are there changes that you'll introduce in upcoming MRs and hence did not add in this one? Next steps of your
feature can also be mentioned here. -->
## Reviewer request
-------------------
- Please provide an ETA when you plan to review this MR. Write a comment to decline or provide an ETA.
- Block the MR if you feel there is less testing or no details in the MR
- Please cover the following aspects in the MR
-- Coding design: _\<Reviewer1>_
-- Backward Compatibility: _\<Reviewer2>_
-- Feature Logic: _\<Logic design\>_
-- _\<Any other context mention here>_
OR
-- _\<Component 1>_: _\<Reviewer1>_
-- _\<CosmosDB>_: _\<Reviewer2>_
-- _\<ServiceBus>_ _\<Reviewer3>_
-- _\<Mention any other component and owner>_
## Other information
-------------------------------------
<!-- Any other information that is important to this MR such as screenshots of how the component looks before and after the change. -->M13 - Release 0.16Harsheet ShahHarsheet Shahhttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/211Bulk create using Cosmos Client2023-08-18T12:43:05ZAnkur RawatBulk create using Cosmos ClientAdded a method to bulk create the records using CosmosClient. CosmosClient can be created either with MSI or Cosmos-primary Key.Added a method to bulk create the records using CosmosClient. CosmosClient can be created either with MSI or Cosmos-primary Key.M13 - Release 0.16Ankur RawatAnkur Rawat