OS Core Lib Azure merge requestshttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests2021-06-24T06:17:49Zhttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/120[WIP] Added support for File Share in core lib azure2021-06-24T06:17:49ZAalekh Jain[WIP] Added support for File Share in core lib azureThis MR targets to add the implementation for File Share in core lib azure.
cc: @vineethguna , @kibattulThis MR targets to add the implementation for File Share in core lib azure.
cc: @vineethguna , @kibattulhttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/119Made changes to do composition of UrlFetchService instead of inheriting it in...2022-12-22T18:58:13ZMuskan SrivastavaMade changes to do composition of UrlFetchService instead of inheriting it in HttpClientAzureM7 - Release 0.10Muskan SrivastavaMuskan Srivastavahttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/118Overloading existing methods in CosmosStore and BlobStore class for system re...2023-08-18T12:44:31ZAman VermaOverloading existing methods in CosmosStore and BlobStore class for system resourcesProblem:
====
The `cosmosStore` class today is the facade to perform CRUD on data partition related cosmos dbs. All the methods in this class are tightly coupled with data-partition-id. Since the system data resources won't be coupled wi...Problem:
====
The `cosmosStore` class today is the facade to perform CRUD on data partition related cosmos dbs. All the methods in this class are tightly coupled with data-partition-id. Since the system data resources won't be coupled with a data-partition-id, the existing facade can't support CRUD on system resources. Same problem exists with `BlobStore` class
Changes in MR:
===
1. Enhanced the current CosmosClientFactory to return system level cosmos clients too.
2. Enhanced the current BlobServiceClientFactory to return system level cosmos clients too.
3. Overloaded existing methods. The new methods don't accept data-partition-id parameter
4. Minor code refactoring
5. Added UTsM7 - Release 0.10Aman VermaAman Vermahttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/117Draft: Added Initial configuration for circuitbreakers2021-06-29T05:25:26ZRonak SakhujaDraft: Added Initial configuration for circuitbreakershttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/116Extending cosmosStore class to support CRUD on system cosmos db2021-06-21T12:28:14ZAman VermaExtending cosmosStore class to support CRUD on system cosmos dbProblem:
====
The `cosmosStore` class today is the facade to perform CRUD on data partition related cosmos dbs. All the methods in this class are tightly coupled with data-partition-id. Since the system data resources won't be coupled wi...Problem:
====
The `cosmosStore` class today is the facade to perform CRUD on data partition related cosmos dbs. All the methods in this class are tightly coupled with data-partition-id. Since the system data resources won't be coupled with a data-partition-id, the existing facade can't support CRUD on system resources.
Changes in MR:
===
1. Enhanced the current CosmosClientFactory to return system level cosmos clients too.
2. Overloaded existing methods. The new methods don't accept data-partition-id parameter
3. Minor code refactoring
Abandoning this MR. Find new MR here: https://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/118Aman VermaAman Vermahttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/115Draft: Gateway mode enabled2021-06-26T08:27:52ZAbhiram BondadaDraft: Gateway mode enabledGateway mode enabled in "createCosmosClient" method of CosmosClientFactoryImplGateway mode enabled in "createCosmosClient" method of CosmosClientFactoryImplAbhiram BondadaAbhiram Bondadahttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/114Draft: Enabling Integrated gateway cache2021-06-14T14:37:46ZAbhiram BondadaDraft: Enabling Integrated gateway cacheAdding gateway mode to "createCosmosClient" in "CosmosClientFactoryImpl.java"Adding gateway mode to "createCosmosClient" in "CosmosClientFactoryImpl.java"Abhiram BondadaAbhiram Bondadahttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/113Enable logging for health check fails2023-08-18T12:44:33ZSmitha ManjunathEnable logging for health check fails## All Submissions:
-------------------------------------
* [YES/NO] 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] I have added te...## All Submissions:
-------------------------------------
* [YES/NO] 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] I have added tests to cover my changes.
* [YES] 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. -->
Currently, there are no logs indicating what components causes health checks to fail.
With the changes made, we can see the logs.
https://dev.azure.com/msazure/One/_sprints/taskboard/Azure%20Global%20Engineering%20Energy%20Team/One/AGE/Cobalt/Jun?workitem=10046151
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?
-------------------------------------
- [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. -->
This is the log seen when tested locally with storage service.
2021-06-10 16:40:26.858 ERROR MININT-DBDIKLJ --- [nio-8081-exec-2] o.o.o.a.h.ActuatorHealthLogger correlation-id= data-partition-id=: Health component keyVault has status DOWN
![image](/uploads/0a6c2099e9a981d98fd452cfbd56ec74/image.png)M7 - Release 0.10Smitha ManjunathSmitha Manjunathhttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/112Reduce info logs for core services2023-08-18T12:44:35ZAlok JoshiReduce info logs for core services## 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.
* [NA] I have added tests ...## 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.
* [NA] I have added tests to cover my changes.
* [YES] All new and existing tests passed.
* [YES] My code follows the code style of this project.
* [NA] I ran lint checks locally prior to submission.
## What is the issue or story related to the change?
-------------------------------------
This change is an effort to reduce info logs for core services. Combining all the AKS services we deploy in our prod, customer environments, we regularly see ContainerLog usage crossing 200 or 300gb daily. Since ApplicationInsight logging is not cheap, this is incurring huge costs.
With this change, we are reducing the number of trace logs that are otherwise not required for 'happy path' for a service request. Please see attached an example of Storage's POST /query/records api request log details from our dev env.
![trace_logs](/uploads/8f8f742ead5aa3291609d5a2f1ed358a/trace_logs.PNG)
The highlighted entries seem unnecessary and given the volume of requests, add up to quite a lot of size. This change aims to remove these entries to cost-optimize logging.
## Test coverage:
------------------
No change
## Does this introduce a breaking change?
-------------------------------------
No
## 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. -->M7 - Release 0.10Alok JoshiAlok Joshihttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/111Draft: Added multi partition support for storage account [2]2021-06-08T08:53:52Zharshit aggarwalDraft: Added multi partition support for storage account [2]https://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/110Multi partition changes for ingestion-workflow2022-12-22T18:58:15ZAalekh JainMulti partition changes for ingestion-workflowChanges done as part of this MR -
1. Added property for ingestion storage account (`ingest-storage-account-key` and `ingest-storage-account-name`) in partition info.
2. Added method in `BlobStore` to generate SAS tokens based on user d...Changes done as part of this MR -
1. Added property for ingestion storage account (`ingest-storage-account-key` and `ingest-storage-account-name`) in partition info.
2. Added method in `BlobStore` to generate SAS tokens based on user delegation key. This MR also resolves the issue of not being able to generate sas tokens using `DefaultAzureCredential`, which is described here in detail: #5.
cc: @harshit283, @abpatil, @kibattul, @polavishnuM7 - Release 0.10https://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/109Fetch only the required event grid topic details2023-08-18T12:44:37ZAlok JoshiFetch only the required event grid topic detailsUpon Storage PUT api (a `recordschanged` event), we are trying to get all event grid properties from partition info, and successively their secret value from KV. This is redundant. As we add other topics for other events, we only want to...Upon Storage PUT api (a `recordschanged` event), we are trying to get all event grid properties from partition info, and successively their secret value from KV. This is redundant. As we add other topics for other events, we only want to pull the event grid properties for the relevant event.
For example, one of the PUTC workflows is adding schemachanged event. Currently, even this property gets pulled (since it matches the regex). This causes 2 issues:
1. If the secrets associated with this property are missing in KV, Storage PUT records workflow doesn't work. This is a major blocker for the most used api
2. This is also causing throttling issues on KV access due to too many reads
This change aims to fix this issue by accessing eventgrid property only relevant to topic nameM7 - Release 0.10Alok JoshiAlok Joshihttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/108Added multi partition support for storage account2021-06-09T05:55:02ZAalekh JainAdded multi partition support for storage accountcc: @harshit283, @abpatilcc: @harshit283, @abpatilhttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/107Configurable Retry And Timeout for Entitlements Service2023-08-18T12:44:40ZMuskan SrivastavaConfigurable Retry And Timeout for Entitlements Service## All Submissions:
-------------------------------------
* I have added an explanation of what changes in this merge do and why we should include it? - YES
* Does the MR contain pipeline/ helm chart related changes?- NO
* I have updated...## All Submissions:
-------------------------------------
* I have added an explanation of what changes in this merge do and why we should include it? - YES
* Does the MR contain pipeline/ helm chart related changes?- NO
* I have updated the documentation accordingly. - YES
* I have added tests to cover my changes. -NA
* 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. -YES
## What is the issue or story related to the change?
-------------------------------------
This change is a step forward to enable the services to configure following variables for service-to-service communication:
- Retry count for service unavailable strategy
- Connect timeout
- Connection Request Timeout
- Socket Timeout
These configurations can only be used for entitlements service for now.
High level design: This MR adds 5 classes in total. <br>
- RetryAndTimeoutConfiguration : contains configuration variables
- HttpClientHandlerAzure : extends HttpClientHandler, and sets variables as picked up by RetryAndTimeoutConfiguration
- HttpClientAzure : uses UrlFetchServiceImpl(which in turn use IHttpClientHandler type) internally, and implements IHttpClient. Currently, Services require a type of IHttpClient to make service-to-service calls
- EntitlementsAPIConfigAzure : creates a bean of type EntitlementsAPIConfig
- EntitlementsFactoryAzure : uses newly created HttpClientAzure internally so that configurable retires can be used for Entitlements Service.
## 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
----------------
Following MRs will be brought further :
- Addition of Factory classes of other services on lines of EntitlementsFactoryAzure will be added.M7 - Release 0.10Muskan SrivastavaMuskan Srivastavahttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/106Draft: Cryptography Retry Configuration2021-12-16T16:23:10ZRonak SakhujaDraft: Cryptography Retry Configuration## All Submissions:
-------------------------------------
* [YES] I have added an explanation of what changes in this merge do and why we should include it?
* [NO] I have updated the documentation accordingly.
* [YES] I have added tests ...## All Submissions:
-------------------------------------
* [YES] I have added an explanation of what changes in this merge do and why we should include it?
* [NO] I have updated the documentation accordingly.
* [YES] I have added tests to cover my changes.
* [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?
-------------------------------------
Cryptographyoffers option for configuring various attributes for retry policy. For any service who wish not to use the default values, and want to provide custom values for the mentioned attributes, they will be able to after this change.
High level design:
![image](/uploads/5d300661ada45b326a9c0043da4f9b89/image.png)
Issue: <!-- Link any __GitLab__ workitem(s) to this pull request. -->
Change details:
Variables that can be added to application.properties are:
azure.cryptography.retryStrategyValue
azure.cryptography.FixedDelayConfiguration.maxRetries
azure.cryptography.FixedDelayConfiguration.delay
azure.cryptography.ExponentialBackoffConfiguration.maxRetrues
azure.cryptography.ExponentialBackoffConfiguration.baseDelayInMillis
azure.cryptography.ExponentialBackoffConfiguration.maxDelayInSeconds
azure.cryptography.retryAfterHeader
azure.cryptography.retryAfterTimeUnit
## Test coverage:
------------------
All changes are covered.
## Does this introduce a breaking change?
-------------------------------------
- NO
## Pending items
----------------
Documentation will come in a separate MR.
## 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. -->https://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/105Added Retry for eventgrid2023-08-18T12:44:41ZRonak SakhujaAdded Retry for eventgrid## 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] I have added tests...## 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] I have added tests to cover my changes.
* [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?
-------------------------------------
Eventgrid offers option for configuring Timeout values. For any service who wish not to use the default values, and want to provide custom values for the mentioned attributes, they will be able to after this change.
High level design:
![image](/uploads/a8ddd03daadbb289f4d25077a9bbc5a2/image.png)
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:
longRunningOperationRetryTimeout can be configured using
azure.eventgridtopic.longRunningOperationRetryTimeout
## Test coverage:
------------------
All changes are covered.
## Does this introduce a breaking change?
-------------------------------------
- YES
<!-- If this introduces a breaking change, please describe the impact and migration path for existing applications below. -->
## Pending items
----------------
## 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. -->M7 - Release 0.10https://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/104Blobstore Retry Configuration2023-08-18T12:44:43ZRonak SakhujaBlobstore Retry Configuration## All Submissions:
-------------------------------------
* [YES] I have added an explanation of what changes in this merge do and why we should include it?
* [NO] I have updated the documentation accordingly.
* [YES] I have added tests ...## All Submissions:
-------------------------------------
* [YES] I have added an explanation of what changes in this merge do and why we should include it?
* [NO] I have updated the documentation accordingly.
* [YES] I have added tests to cover my changes.
* [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?
-------------------------------------
BlobStore offers option for configuring various attributes for retry policy. For any service who wish not to use the default values, and want to provide custom values for the mentioned attributes, they will be able to after this change.
High level design:
![image](/uploads/5d300661ada45b326a9c0043da4f9b89/image.png)
Issue: <!-- Link any __GitLab__ workitem(s) to this pull request. -->
Change details:
Variables that can be added to application.properties are:
azure.blobstore.maxTries
azure.blobstore.tryTimeoutInSeconds
azure.blobstore.retryDelayInMs
azure.blobstore.maxRetryDelayInMs
azure.blobstore.retryPolicyType
azure.blobstore.secondaryHost
## Test coverage:
------------------
All changes are covered.
![image](/uploads/93e03dc4635021ba219dbefad4cdbca1/image.png)
## Does this introduce a breaking change?
-------------------------------------
- NO
## Pending items
----------------
## 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. -->M7 - Release 0.10https://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/103Rosakhuj/cosmos22021-06-20T09:46:59ZRonak SakhujaRosakhuj/cosmos2Duplicate of https://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/98
## All Submissions:
-------------------------------------
* [YES] I have added an explanation of what changes in this...Duplicate of https://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/98
## All Submissions:
-------------------------------------
* [YES] I have added an explanation of what changes in this merge do and why we should include it?
* [NO] I have updated the documentation accordingly.
* [YES] I have added tests to cover my changes.
* [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?
-------------------------------------
CosmosDB offers option for configuring MaxRetryAttempts and MaxRetryWaitTime. For any service who wish not to use the default values, and want to provide custom values for the mentioned attributes, they will be able to after this change.
High level design:
![image](/uploads/24e32c7ff6c8541f98fed70324aa998b/image.png)
Issue: <!-- Link any __GitLab__ workitem(s) to this pull request. -->
We are adding some configurable options for retries in CosmosDB to common.properties. Services can override these properties through application.properties and set their own custom values.
Sample values
azure.cosmos.maxRetryCount=9
azure.cosmos.retryWaitTimeout=30
## 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. -->
## 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. -->https://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/102WIP: Added retry config to blobstorage2021-05-25T16:35:51ZRonak SakhujaWIP: Added retry config to blobstoragehttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/101Upgrade os-core-common library2023-08-18T12:44:45ZRostislav Vatolinvatolinrp@gmail.comUpgrade os-core-common libraryUpgraded library os-core-common to 0.9.0-rc13 so latest changes related to elasticsearch libraries are applied.
The latest version of os-core-common has ILogger interface updated: included debug methods. Having that, the new methods were...Upgraded library os-core-common to 0.9.0-rc13 so latest changes related to elasticsearch libraries are applied.
The latest version of os-core-common has ILogger interface updated: included debug methods. Having that, the new methods were implemented in Slf4JLogger class.
The new library was tested with the following service: crs-catalog-service: https://community.opengroup.org/osdu/platform/system/reference/crs-catalog-service/-/merge_requests/47M6 - Release 0.9