1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
|
# Release History
## 1.0.0b1 (2020-12-02)
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/master/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/master/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/master/sdk/core/azure-core-tracing-opentelemetry) for an overview.
## 0.4.0 (2020-05-29)
**Features**
- Model ServiceSpecification has a new parameter log_specifications
- Model SignalRResource has a new parameter network_ac_ls
- Model SignalRResource has a new parameter upstream
- Model SignalRResource has a new parameter private_endpoint_connections
- Model SignalRResource has a new parameter kind
- Model Operation has a new parameter is_data_action
- Model SignalRCreateOrUpdateProperties has a new parameter upstream
- Model SignalRCreateOrUpdateProperties has a new parameter network_ac_ls
- Added operation group SignalRPrivateEndpointConnectionsOperations
- Added operation group SignalRPrivateLinkResourcesOperations
**General Breaking Changes**
This version uses a next-generation code generator that *might*
introduce breaking changes. 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.
- SignalRClient cannot be imported from
`azure.mgmt.signalr.signalr_client` anymore (import from
`azure.mgmt.signalr` works like before)
- SignalRClientConfiguration import has been moved from
`azure.mgmt.signalr.signalr_client`
to `azure.mgmt.signalr`
- A model `MyClass` from a "models" sub-module cannot be imported
anymore using `azure.mgmt.signalr.models.my_class` (import from
`azure.mgmt.signalr.models` works like before)
- An operation class `MyClassOperations` from an `operations`
sub-module cannot be imported anymore using
`azure.mgmt.signalr.operations.my_class_operations` (import from
`azure.mgmt.signalr.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.3.0 (2019-08-06)
**Features**
- Model SignalRResource has a new parameter cors
- Model SignalRResource has a new parameter features
- Model SignalRCreateOrUpdateProperties has a new parameter cors
- Model SignalRCreateOrUpdateProperties has a new parameter feature
## 0.2.0 (2019-05-21)
- Add restart operation
## 0.1.1 (2018-09-04)
**Features**
- Model SignalRKeys has a new parameter secondary_connection_string
- Model SignalRKeys has a new parameter primary_connection_string
- Model MetricSpecification has a new parameter dimensions
- Model SignalRResource has a new parameter version
- Added operation group UsagesOperations
## 0.1.0 (2018-05-07)
- Initial Release
|
