OS Core Lib Azure merge requestshttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests2022-09-25T13:24:39Zhttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/198Upgrade First Party Library Dependencies for Release 0.142022-09-25T13:24:39ZDavid Diederichd.diederich@opengroup.orgUpgrade First Party Library Dependencies for Release 0.14This 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: d385bfe074d62ddd25afe73165e7dc00544f1784
Maven: 0.14.0-SNAPSHOT
```
| Maven Dependencies | _Root_ |
| ------------------ | ---------- |
| os-core-common | 0.14.0-rc1 |
### Dependency Information After the Upgrade
```
Branch: dependency-upgrade
SHA: c4777b62c65f10469b54c498e97e107dcbb54e70
Maven: 0.14.0-SNAPSHOT
```
| Maven Dependencies | _Root_ |
| ------------------ | ------ |
| os-core-common | 0.14.0 |M11 - Release 0.14https://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/195Add Method for generating SAS token in blobstore2023-08-18T12:43:17Zharshit aggarwalAdd Method for generating SAS token in blobstoreM11 - Release 0.14harshit aggarwalharshit aggarwalhttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/194Adding tests for KeyVaultFacade and RedisClientFactory2022-12-22T18:58:03ZShiv SinghAdding tests for KeyVaultFacade and RedisClientFactoryShiv SinghShiv Singhhttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/193Standardize worker logs2023-08-18T12:43:19ZVibhuti Sharma [Microsoft]Standardize worker logs**Aim**
Enable worker services to follow a common logging format.
**Implementation**
* Added an Abstract class for MessageHandler class that is defined in worker services like WKS and Indexer Queue, to follow a common start and end work...**Aim**
Enable worker services to follow a common logging format.
**Implementation**
* Added an Abstract class for MessageHandler class that is defined in worker services like WKS and Indexer Queue, to follow a common start and end worker log template.
* Added WorkerPayload class in logging module, along with logWorker method in CoreLogger
**Related MRs**
* https://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/382/diffsM11 - Release 0.14Vibhuti Sharma [Microsoft]Vibhuti Sharma [Microsoft]https://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/192Adding RedisAzureConfiguration for RedisAzureCache2022-12-22T18:58:02ZShiv SinghAdding RedisAzureConfiguration for RedisAzureCache## 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. -->Shiv SinghShiv Singhhttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/191Cherry-pick 'ankurrawat/storageBlobVersionUpdate' into 'release/0.13'2022-12-22T18:58:02ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'ankurrawat/storageBlobVersionUpdate' into 'release/0.13'Original MR: !188Original MR: !188https://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/190Adding MSI Authentication for Azure Resource2023-08-18T12:43:21Zharshit aggarwalAdding MSI Authentication for Azure ResourceM11 - Release 0.14harshit aggarwalharshit aggarwalhttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/188increased version for storage blob2023-08-18T12:43:22ZAnkur Rawatincreased version for storage blobFluxutil is available in azure-core package for version >= 1.17.0Fluxutil is available in azure-core package for version >= 1.17.0M11 - Release 0.14Ankur RawatAnkur Rawathttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/187Fix Notice2023-08-18T12:43:24Zharshit aggarwalFix NoticeM11 - Release 0.14harshit aggarwalharshit aggarwalhttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/186Add option to use MSI for Authentication to Azure Resources2023-08-18T12:43:26Zharshit aggarwalAdd option to use MSI for Authentication to Azure ResourcesChanges in the MR are focused on adding option to use Managed Identity Credentials while authenticating to Azure resourcesChanges in the MR are focused on adding option to use Managed Identity Credentials while authenticating to Azure resourcesM11 - Release 0.14harshit aggarwalharshit aggarwalhttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/184Cherry-pick 'Make DataLakeProvider a conditional bean' into 'release/0.13'2022-12-22T18:58:03ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Make DataLakeProvider a conditional bean' into 'release/0.13'Original MR: !183Original MR: !183M10 - Release 0.13David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/183Make DataLakeProvider a conditional bean2023-08-18T12:43:27ZRostislav Vatolinvatolinrp@gmail.comMake DataLakeProvider a conditional beanFixes https://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/issues/19Fixes https://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/issues/19M11 - Release 0.14https://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/182Upgrading core library dependencies2022-01-25T01:08:43ZDavid Diederichd.diederich@opengroup.orgUpgrading core library dependenciesM10 - Release 0.13David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/181Revert back to 0.13.0-SNAPSHOT2022-01-24T16:15:44ZDavid Diederichd.diederich@opengroup.orgRevert back to 0.13.0-SNAPSHOTThe 0.13.1-SNAPSHOT artifact version is used by the release/0.13 branch to prepare for the first patch of 0.13 (that is,
0.13.1). Utilizing the version here on the default branch will create packages that could interfere with that develo...The 0.13.1-SNAPSHOT artifact version is used by the release/0.13 branch to prepare for the first patch of 0.13 (that is,
0.13.1). Utilizing the version here on the default branch will create packages that could interfere with that development line when
it comes into existence.
Additionally, other logic that attempts to find the latest version will return 0.13.1-SNAPSHOT as being newer than 0.13.0 (full
release), even though this isn't true. When used in the release branch, this relationship does hold -- development in preparation
for the first patch _is_ newer than the last release.M10 - Release 0.13David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/180Removing unused variables2023-08-18T12:43:29ZAbhishek Kumar (SLB)Removing unused variablesFix for the issue described here: https://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/issues/17Fix for the issue described here: https://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/issues/17M11 - Release 0.14Abhishek Kumar (SLB)Paresh BehedeAbhishek Kumar (SLB)https://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/179Remove extra curly brace on dependency.2022-01-21T11:55:37ZDavid Diederichd.diederich@opengroup.orgRemove extra curly brace on dependency.This was most likely a simple typoThis was most likely a simple typoM10 - Release 0.13David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/178Created wrapper for Redis to de-couple availability of redis with service hea...2023-08-18T12:43:31ZKrishna Nikhil VedurumudiCreated wrapper for Redis to de-couple availability of redis with service health.## All Submissions:
-------------------------------------
* [YES] I have added an explanation of what changes in this merge do and why we should include it?
* [YES] I have updated the documentation accordingly.
* [YES/NO/NA] I have added...## All Submissions:
-------------------------------------
* [YES] I have added an explanation of what changes in this merge do and why we should include it?
* [YES] I have updated the documentation accordingly.
* [YES/NO/NA] I have added tests to cover my changes. - TBD - Opened up for initial review
* [YES] All new and existing tests passed.
* [YES] My code follows the code style of this project.
* [YES] 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:
Created a wrapper for RedisCache `RedisAzureCache` that would be wired up the services even without availability of the Redis cache infrastructure.
This enables us to de-couple Redis availability with Service health. i.e., Redis unavailability will cause service degradation rather than outage.
## Test coverage:
------------------
<!-- Mention unit test coverage of changes. -->
## Does this introduce a breaking change?
-------------------------------------
- [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. -->
## Other information
-------------------------------------
<!-- Any other information that is important to this MR such as screenshots of how the component looks before and after the change. -->M11 - Release 0.14Krishna Nikhil VedurumudiKrishna Nikhil Vedurumudihttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/176Resolve "Upgrade to Log4J 2.17.1 to address CVE-2021-44832"2022-01-18T19:23:41ZDavid Diederichd.diederich@opengroup.orgResolve "Upgrade to Log4J 2.17.1 to address CVE-2021-44832"Closes #16Closes #16M10 - Release 0.13David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/175Data lake store2023-08-18T12:43:33ZHarshit SaxenaData lake storeIn these changes, I am adding the Azure DataLake Gen 2 store which will be used by the file collection feature.
Changes -
1) create directory in Azure DataLake file System
2) generate signed URL for Azure DataLake file System's directory.In these changes, I am adding the Azure DataLake Gen 2 store which will be used by the file collection feature.
Changes -
1) create directory in Azure DataLake file System
2) generate signed URL for Azure DataLake file System's directory.M10 - Release 0.13Harshit SaxenaHarshit Saxenahttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/174Cherry-pick log4j updates into the release branch2021-12-20T20:26:57ZDavid Diederichd.diederich@opengroup.orgCherry-pick log4j updates into the release branchOriginal MR: !173
Part of the #15 seriesOriginal MR: !173
Part of the #15 seriesDavid Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.org