OS Core Lib Azure merge requestshttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests2024-02-15T07:02:26Zhttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/332429 exception handling for bulk update operation in storage2024-02-15T07:02:26ZAnkur Rawat429 exception handling for bulk update operation in storageCurrently, bulk insertion in cosmos DB functionality returns 500 in case of 429 error form cosmos DB. Updated the functionality to send 429 received from Cosmos DBCurrently, bulk insertion in cosmos DB functionality returns 500 in case of 429 error form cosmos DB. Updated the functionality to send 429 received from Cosmos DBAnkur RawatAnkur Rawathttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/83Adapters for PartitionInfo2021-11-19T12:10:12ZKomal MakkarAdapters for PartitionInfo## All Submissions:
-------------------------------------
* [YES] I have added an explanation of what changes in this merge do and why we should include it?
* [NO] Does the MR contain pipeline/ helm chart related changes?
* [YES] I have ...## All Submissions:
-------------------------------------
* [YES] I have added an explanation of what changes in this merge do and why we should include it?
* [NO] Does the MR contain pipeline/ helm chart related changes?
* [YES] I have updated the documentation accordingly.
* [NA] 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.
## 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. -->
*Note*: The MR is not an implementation MR. Hence, please don't expect tests to be in place.
**Existing Behaviour**: The PartitionInfo is not consumable easily. PartitionInfoAzure was the means to consume it. The deserialization had hardcoded the keys of the map. This limits us to add keys on the fly and consume those.
The right-hand side is the representation of how we are consuming it today.
**Modified Behaviour**:
The left hand represents the modified behavior. We can break it down as follows to understand it better.
1. Breaking free from PartitionInfoAzure. We encourage Data Models for each resource type, for instance, EventGridPartitionConfig.
2. Adapter for creating the config. These adapters are supposed to convert PartitionInfoAzure to Config data model. For instance EventGridPartitionConfigAdapter.
3. PartitionInfoProvider. This provider is meant to make sure the infra stores have the access to PartitionInfo. PartitionInfo is supplied to the adapters.
High level design:
![image](/uploads/9344487aca80e938f91df51a7e072342/image.png)
Issue: <!-- Link any __GitLab__ workitem(s) to this pull request. -->
#6
<!-- 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] 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/207add AbstractMessageHandlerWithActiveRetry implementation for service bus mess...2022-05-25T12:09:24ZYauheni Lesnikauadd AbstractMessageHandlerWithActiveRetry implementation for service bus message handler## 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?
-------------------------------------
<!-- 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: https://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/issues/22
<!-- 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: I've added new class `AbstractMessageHandlerWithActiveRetry` which extends the `AbstractMessageHandler` which provides functionality for the retry management.Yauheni LesnikauYauheni Lesnikauhttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/44Add a common logger interface2023-08-18T12:46:08ZKelly DomicoAdd a common logger interfaceThis MR adds the following:
1. A common interface that supports collecting information to meet observability/monitoring requirements. This interface provides methods to log traces at various severity levels (i.e. info, warning, error), ...This MR adds the following:
1. A common interface that supports collecting information to meet observability/monitoring requirements. This interface provides methods to log traces at various severity levels (i.e. info, warning, error), audit events and dependencies. The specific implementations of this interface have the freedom to choose how and where to store the logs.
2. An implementation of the interface that logs to Application Insights using a Log4J2 appender and the SLF4J API. Traces are logged using the SLF4J-provided info, warn and error methods. Exceptions are automatically forwarded to the "exceptions" Application Insights table.
Example usage:
```
ICoreLogger logger = CoreLoggerProvider.getInstance().getLogger(SomeClass.class);
logger.info("Log this message");
```M1 - Release 0.1https://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/273add async version of QUERY_ITEMS_API (CosmosAsyncClient)2023-01-12T10:38:20ZYurii Kondakovadd async version of QUERY_ITEMS_API (CosmosAsyncClient)Currently, using the existing client (Sync API), a certain number of extra (prefetch) queries are performed when retrieve records from the database page by page. This increases the consumption of Cosmos DB Requests Units (RUs).
To preven...Currently, using the existing client (Sync API), a certain number of extra (prefetch) queries are performed when retrieve records from the database page by page. This increases the consumption of Cosmos DB Requests Units (RUs).
To prevent this, an asynchronous client and an appropriate method for retrieving records from the database using this asynchronous client have been added.
[Issue](https://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/issues/29)M16 - Release 0.19Yurii KondakovYurii Kondakovhttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/223Add Azure Audit Appender and Logger2023-08-18T12:42:56ZAkshat JoshiAdd Azure Audit Appender and LoggerM14 - Release 0.17https://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/125Add circuitbreaker to all inter service communication2023-08-18T12:44:28ZRonak SakhujaAdd circuitbreaker to all inter service communication## 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?
-------------------------------------
We are adding a circuitbreaker to all Interservice communication. All Services use HTTPClient's send method to make requests. In this MR, we are decorating the send method with a circuibreaker to avoid the problem of cascading fallback.
Be default, we are using default configurations of circuibreaker. Values can be found here(https://resilience4j.readme.io/docs/circuitbreaker#create-and-configure-a-circuitbreaker)
High level design:
![image](/uploads/6e831b2eafffb873f6f38632b4a69339/image.png)
CircuitBreaker is at the service level. At pod level communication, the URL for let's say entitlements service is defined as : http://entitlements/api/entitlements/v2 . We will fetch the host and make it as the key for circuitbreaker.
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:
We are adding a circuitbreakersingleton class to keep the circuitbreakerregistry. There is a flag which can be set to enable circuitbreaker for a service.
When circuitbreaks, it will start throwing error 500 without making http call.
## Test coverage & Tests:
------------------
<!-- Mention unit test coverage of changes. -->
Used Storage service and Entitlements service for testing.
While Entitlements was up, sent HttpRequests from Storage to Entitlements with success response.
Turned off Entitlements service and then sent requests from storage to entitlements which resulted in errors.
After the required number of calls, obtained log that circuit has opened and post which the requests were failing fast.
Tested the behavior by running on kubernetes cluster locally.
## Test on perf environment
I setup Storage and Entitlements on perf, and added a preauthorize on healthcheck in storage.
Scenario : Storage service calling entitlements
1. Behaviour when Entitlements is up :
![image](/uploads/194977dcf756eac71598260ec8226c7b/image.png)
2. Behaviour when Entitlements is down and circuit is closed :
![image](/uploads/aa6813f973711dd823d2aa86576433de/image.png)
3. Behaviour when Failure threshold is crossed and circuit is open :
![image](/uploads/6afaddc06ddf30d92d48f4d474cc09a1/image.png)
UPDATE : When Circuit is open, we are throwing Exception 503 : Service Unavailable
Logs generated when circuit gets open :
![image](/uploads/93788b1e68e14996451f02c5b8490897/image.png)
Tested to ensure multiple circuitbreakers for different services can be maintained.
## 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
----------------
1. Make all configuration of circuitbreaker configurable.
2. Segregate circuitbreakers to remove parameters from circuitbreaker name
## 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. -->M8 - Release 0.11https://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/92Add configuration properties for event-grid & cryptography factories, partiti...2023-08-18T12:44:59ZNeelesh ThakurAdd configuration properties for event-grid & cryptography factories, partition service initialization fails otherwiseAzure resources are partition aware, they will try to initialize partition service client when they are integrated with Core services. In case of Partition service, it's not desired behavior. Partition service do rely on core-lib-azure f...Azure resources are partition aware, they will try to initialize partition service client when they are integrated with Core services. In case of Partition service, it's not desired behavior. Partition service do rely on core-lib-azure for common azure functionality so we cannot take out the core-lib-azure reference from service. These config property will allow us to disable injection of these factories.M6 - Release 0.9https://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/55Add dependency logging to CosmosStore2023-08-18T12:45:49ZKelly DomicoAdd dependency logging to CosmosStoreAdd dependency logging (via CoreLogger) to CosmosStore so we can track calls from the service to CosmosDB. Additionally add trace logging for successful calls.
Additional small fix to DependencyPayload parameter descriptions.Add dependency logging (via CoreLogger) to CosmosStore so we can track calls from the service to CosmosDB. Additionally add trace logging for successful calls.
Additional small fix to DependencyPayload parameter descriptions.M3 - Release 0.5Kishore BattulaVibhuti Sharma [Microsoft]Kishore Battulahttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/235add dependency logs to bulk cosmos apis2022-09-15T08:29:19ZNeelesh Thakuradd dependency logs to bulk cosmos apisAdds dependency logs to bulk CosmosDB APIs
## 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 documenta...Adds dependency logs to bulk CosmosDB APIs
## 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?
-------------------------------------
Add dependency logs to bulk CosmosDB APIs
## Test coverage:
------------------
Added and updated tests.
## Does this introduce a breaking change?
-------------------------------------
- [NO]M14 - Release 0.17https://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/285Add document id in bulk errros2023-03-10T16:30:38ZAlok JoshiAdd document id in bulk errrosUse cosmosItemOperation.getId() instead of cosmosItemOperation.getItem() to keep the message small
Return document id with errors when performing bulk operation
Will be useful in implementing [ADR](https://community.opengroup.org/osdu/...Use cosmosItemOperation.getId() instead of cosmosItemOperation.getItem() to keep the message small
Return document id with errors when performing bulk operation
Will be useful in implementing [ADR](https://community.opengroup.org/osdu/platform/system/storage/-/issues/124) to get info on recordIds in case of failureM17 - Release 0.20Alok JoshiAlok Joshihttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/54Add doNothing to CoreLoggerTest so test data isn't logged2021-01-07T21:38:59ZKelly DomicoAdd doNothing to CoreLoggerTest so test data isn't loggedAdd doNothing to CoreLoggerTest so test data isn't loggedAdd doNothing to CoreLoggerTest so test data isn't loggedKishore BattulaKishore Battulahttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/255Added a regex filter to filter out a particular pattern of msgs received from...2023-08-18T12:42:35ZNaga Aneesh MylavarapuAdded a regex filter to filter out a particular pattern of msgs received from core message receiver## 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. -->
https://dev.azure.com/OpenEnergyPlatform/Open%20Energy%20Platform/\_sprints/taskboard/Energy%20-%20Explorers/Open%20Energy%20Platform/Oct%20'22/Oct%20'22%20Sprint%203?workitem=7737
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: Added a regex filter to filter out messages of a particular pattern received from CoreMessageReceiver. Added a threshold filter to ensure that messages are removed only if their level is info or below.
## Test coverage:
------------------
<!-- Mention unit test coverage of changes. -->
## Does this introduce a breaking change?
-------------------------------------
- [YES/NO] 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. -->M15 - Release 0.18Naga Aneesh MylavarapuNaga Aneesh Mylavarapuhttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/82Added Async blob store2021-11-19T12:09:54ZNicholas KarskyAdded Async blob store## 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?
-------------------------------------
Adding the factory files necessary to implement BlockBlobAsyncClient for blob uploads
High level design:
Introduces use of Flux and Mono in order to speed up the blob upload process
## Test coverage:
------------------
100% coverage
## Does this introduce a breaking change?
-------------------------------------
- [NO]
## Pending items
----------------
N/A
## 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. -->Nicholas KarskyNicholas Karskyhttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/49Added BlobStore provider to create spring beans for BlobStore related classes2023-08-18T12:45:57ZKishore BattulaAdded BlobStore provider to create spring beans for BlobStore related classesM1 - Release 0.1https://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/153Added code to disable ai appender based on jvm argument2023-08-18T12:43:55ZVineeth Guna [Microsoft]Added code to disable ai appender based on jvm argumentM9 - Release 0.12https://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/10Added config based Enable/disable of SSL for elastic search for debugging2023-08-18T12:47:01ZHema Vishnu Pola [Microsoft]Added config based Enable/disable of SSL for elastic search for debugging## All Submissions:
-------------------------------------
* [YES] Have you added an explanation of what your changes do and why you'd like us to include them?
* [YES] I have updated the documentation accordingly.
* [YES/NO/NA] I have add...## All Submissions:
-------------------------------------
* [YES] Have you added an explanation of what your changes do and why you'd like us to include them?
* [YES] 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.
## Current Behavior or Linked Issues
-------------------------------------
Issue details: https://community.opengroup.org/osdu/platform/system/home/-/issues/39
## Does this introduce a breaking change?
-------------------------------------
- [NO]
This doesn't bring in any breaking changes.
*Added a new function that allows to fetch key vault secrets with a default used that is passed.*
## Other information
-------------------------------------
- Elastic search SSL endpoint can now be controlled by setting 'elastic-ssl-enabled' to true or false.M1 - Release 0.1Hema Vishnu Pola [Microsoft]Hema Vishnu Pola [Microsoft]https://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/98Added Configurable retries to Cosmos2023-08-18T12:44:49ZRonak SakhujaAdded Configurable retries to Cosmos## 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?
-------------------------------------
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. -->
All changes are covered.
All ITs passed
![image](/uploads/44d9da1896144dba82d15f0eb6633354/image.png)
## 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. -->M7 - Release 0.10Ronak SakhujaRonak Sakhujahttps://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/149Added @Configuration2023-08-18T12:44:00ZRonak SakhujaAdded @ConfigurationSpring doesn't create bean if @Configuration is not present. Hence adding @Configuration to config classSpring doesn't create bean if @Configuration is not present. Hence adding @Configuration to config classM9 - Release 0.12https://community.opengroup.org/osdu/platform/system/lib/cloud/azure/os-core-lib-azure/-/merge_requests/121Added configuration related to airflow in PartitionInfoAzure2023-08-18T12:44:30ZVineeth Guna [Microsoft]Added configuration related to airflow in PartitionInfoAzureM7 - Release 0.10