Skip to content

Commit

Permalink
Update from release/v3
Browse files Browse the repository at this point in the history
  • Loading branch information
SDK Automation committed Jul 8, 2020
1 parent 2ba23a5 commit c0cc08b
Show file tree
Hide file tree
Showing 3 changed files with 113 additions and 153 deletions.
41 changes: 0 additions & 41 deletions sdk/signalr/azure-mgmt-signalr/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,46 +1,5 @@
# Release History

## 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**
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -9,5 +9,5 @@
# regenerated.
# --------------------------------------------------------------------------

VERSION = "0.4.0"
VERSION = "0.3.0"

Loading

0 comments on commit c0cc08b

Please sign in to comment.