azure-mgmt-alertsmanagement 0.2.0rc2

0.2.0rc2 (2019-07-31)

Bugfix

• Fixed autogenerated code problems

0.2.0rc1 (2019-07-29)

Features

• Added operation AlertsOperations.meta_data

• Added operation group SmartDetectorAlertRulesOperations

• Added operation group ActionRulesOperations

General breaking changes

This version uses a next-generation code generator that might introduce breaking changes if from some import. 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.

• AlertsManagementClient cannot be imported from azure.mgmt.alertsmanagement.alerts_management_client anymore (import from azure.mgmt.alertsmanagement works like before)

• AlertsManagementClientConfiguration import has been moved from azure.mgmt.alertsmanagement.alerts_management_client to azure.mgmt.alertsmanagement

• A model MyClass from a “models” sub-module cannot be imported anymore using azure.mgmt.alertsmanagement.models.my_class (import from azure.mgmt.alertsmanagement.models works like before)

• An operation class MyClassOperations from an operations sub-module cannot be imported anymore using azure.mgmt.alertsmanagement.operations.my_class_operations (import from azure.mgmt.alertsmanagement.operations works like before)

Last but not least, HTTP connection pooling is now enabled by default. You should always use a client as a context manager, or call close(), or use no more than one client per process.

0.1.0 (2018-09-17)

• Initial Release