# Release History

## 2.0.0b2 (2022-12-26)

### Features Added

  - Added operation group PrometheusRuleGroupsOperations

## 2.0.0b1 (2022-08-22)

### Features Added

  - Added operation group AlertProcessingRulesOperations
  - Model Condition has a new parameter field
  - Model Essentials has a new parameter action_status
  - Model Essentials has a new parameter description
  - Model Operation has a new parameter origin
  - Model PatchObject has a new parameter enabled

### Breaking Changes

  - Model PatchObject no longer has parameter status
  - Operation AlertsOperations.change_state has a new parameter comment
  - Removed operation group ActionRulesOperations
  - Removed operation group SmartDetectorAlertRulesOperations

## 1.0.0 (2021-03-16)

- GA release

## 1.0.0b1 (2020-11-20)

This is beta preview version.

This version uses a next-generation code generator that introduces important breaking changes, but also important new features (like unified authentication and async programming).

**General breaking changes**

- Credential system has been completly revamped:

  - `azure.common.credentials` or `msrestazure.azure_active_directory` instances are no longer supported, use the `azure-identity` classes instead: https://pypi.org/project/azure-identity/
  - `credentials` parameter has been renamed `credential`

- The `config` attribute no longer exists on a client, configuration should be passed as kwarg. Example: `MyClient(credential, subscription_id, enable_logging=True)`. For a complete set of
  supported options, see the [parameters accept in init documentation of azure-core](https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/core/azure-core/CLIENT_LIBRARY_DEVELOPER.md#available-policies)
- You can't import a `version` module anymore, use `__version__` instead
- Operations that used to return a `msrest.polling.LROPoller` now returns a `azure.core.polling.LROPoller` and are prefixed with `begin_`.
- Exceptions tree have been simplified and most exceptions are now `azure.core.exceptions.HttpResponseError` (`CloudError` has been removed).
- Most of the operation kwarg have changed. Some of the most noticeable:

  - `raw` has been removed. Equivalent feature can be found using `cls`, a callback that will give access to internal HTTP response for advanced user
  - For a complete set of
  supported options, see the [parameters accept in Request documentation of azure-core](https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/core/azure-core/CLIENT_LIBRARY_DEVELOPER.md#available-policies)

**General new features**

- Type annotations support using `typing`. SDKs are mypy ready.
- This client has now stable and official support for async. Check the `aio` namespace of your package to find the async client.
- This client now support natively tracing library like OpenCensus or OpenTelemetry. See this [tracing quickstart](https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/core/azure-core-tracing-opentelemetry) for an overview.


## 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