Dependency Management & Azure SDK Upgrade
All Submissions:
- [YES] Have you followed our code review guidelines?
- [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.
- [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.
- [NO] I ran lint checks locally prior to submission.
What is the current behavior?
- Old version of Azure SDKs are used in service.
- Versions of dependencies which are common across all OSDU services are not consistent/same in all OSDU services.
What is the new behavior?
- All Azure SDKs are upgraded to latest stable version.
- Common dependencies are inherited from core-lib-azure as managed dependencies. This will make sure that version info of those dependencies are inherited from core-lib-azure. All OSDU services using same version of core-lib-azure will automatically use same versions for all those dependencies.
- Changes to support new cosmos-store & azure-cosmos sdk version.
- Changes to make service work for single partition (opendes) and bypass partition service.
Does this introduce a breaking change?
- [NO]
Any relevant logs, error output, etc?
(If it’s long, please paste to https://ghostbin.com/ and insert the link here.)
Other information
Merge request reports
Activity
added Azure label
@harshit283 please have a look
- Resolved by Abhishek Patil
- Resolved by Abhishek Patil
added 1 commit
- b8e5dfef - Disabling keyvault & using updated core-lib-azure
added 16 commits
-
b8e5dfef...cfa3f011 - 10 commits from branch
master
- 8212ab64 - Using latest core-lib-azure
- e5d6bcdb - Support for single partition & bypass partition service
- bdc1b4bc - Removing temporary changes
- 29cee1fb - Using properties for defining version
- 9ff12a63 - Using actual parameter instead of any()
- 99c3a5af - Disabling keyvault & using updated core-lib-azure
Toggle commit list-
b8e5dfef...cfa3f011 - 10 commits from branch
enabled an automatic merge when the pipeline for 99c3a5af succeeds
enabled an automatic merge when the pipeline for 8f9e7de5 succeeds
- Resolved by Abhishek Patil
@harshit283 @abpatil - Take a look at this MR and see if we are good to close it.
added 27 commits
-
8f9e7de5...c219e75f - 26 commits from branch
master
- dde9f6b9 - Merge branch 'master' into abpatil/dpndncy_mngmnt_az_sdk_upgrd
-
8f9e7de5...c219e75f - 26 commits from branch
Please register or sign in to reply