From 59f00ce36c2717778a67200e79e9723f7f50c514 Mon Sep 17 00:00:00 2001 From: zikalino Date: Thu, 15 Aug 2019 13:27:35 +0800 Subject: [PATCH] one more fix --- sdk/cosmos/azure-mgmt-cosmosdb/HISTORY.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sdk/cosmos/azure-mgmt-cosmosdb/HISTORY.rst b/sdk/cosmos/azure-mgmt-cosmosdb/HISTORY.rst index 0c7210cde4cb..acba458173bd 100644 --- a/sdk/cosmos/azure-mgmt-cosmosdb/HISTORY.rst +++ b/sdk/cosmos/azure-mgmt-cosmosdb/HISTORY.rst @@ -19,7 +19,7 @@ This version uses a next-generation code generator that *might* introduce breaki In summary, some modules were incorrectly visible/importable and have been renamed. This fixed several issues caused by usage of classes that were not supposed to be used in the first place. - CosmosDB cannot be imported from `azure.mgmt.cosmosdb.cosmos_db` anymore (import from `azure.mgmt.cosmosdb` works like before) -- CosmosDBConfiguration import has been moved from `azure.mgmt.cosmosdb.cosmos_db_client` to `azure.mgmt.cosmosdb` +- CosmosDBConfiguration import has been moved from `azure.mgmt.cosmosdb.cosmos_db` to `azure.mgmt.cosmosdb` - A model `MyClass` from a "models" sub-module cannot be imported anymore using `azure.mgmt.cosmosdb.models.my_class` (import from `azure.mgmt.cosmosdb.models` works like before) - An operation class `MyClassOperations` from an `operations` sub-module cannot be imported anymore using `azure.mgmt.cosmosdb.operations.my_class_operations` (import from `azure.mgmt.cosmosdb.operations` works like before)