Microsoft Azure SDK for Python

This is the Microsoft Azure Deployment Manager Client Library. This package has been tested with Python 3.7+. For a more complete view of Azure libraries, see the azure sdk python release.

Disclaimer

Azure SDK Python packages support for Python 2.7 has ended 01 January 2022. For more information and questions, please refer to https://github.com/Azure/azure-sdk-for-python/issues/20691

Usage

To learn how to use this package, see the quickstart guide

For docs and references, see Python SDK References Code samples for this package can be found at Deployment Manager on docs.microsoft.com. Additional code samples for different Azure services are available at Samples Repo

Provide Feedback

If you encounter any bugs or have suggestions, please file an issue in the Issues section of the project.

Release History

2.0.0b1 (2022-11-01)

Features Added

• Model RolloutProperties has a new parameter artifact_source_id

Breaking Changes

• Model RolloutProperties has a new required parameter build_version
• Model RolloutProperties has a new required parameter step_groups
• Model RolloutProperties has a new required parameter target_service_topology_id
• Model RolloutPropertiesAutoGenerated no longer has parameter artifact_source_id
• Model RolloutPropertiesAutoGenerated no longer has parameter build_version
• Model RolloutPropertiesAutoGenerated no longer has parameter step_groups
• Model RolloutPropertiesAutoGenerated no longer has parameter target_service_topology_id

1.0.0 (2021-05-20)

Features

• Model RolloutPropertiesAutoGenerated has a new parameter artifact_source_id

Breaking changes

• Operation StepsOperations.list has a new signature
• Operation ServicesOperations.list has a new signature
• Operation ServicesOperations.list has a new signature
• Operation ServiceTopologiesOperations.list has a new signature
• Operation ServiceTopologiesOperations.get has a new signature
• Operation ServiceTopologiesOperations.get has a new signature
• Operation RolloutsOperations.list has a new signature
• Operation ArtifactSourcesOperations.list has a new signature
• Model RolloutProperties no longer has parameter step_groups
• Model RolloutProperties no longer has parameter target_service_topology_id
• Model RolloutProperties no longer has parameter build_version
• Model RolloutProperties no longer has parameter artifact_source_id
• Model RolloutPropertiesAutoGenerated has a new required parameter step_groups
• Model RolloutPropertiesAutoGenerated has a new required parameter target_service_topology_id
• Model RolloutPropertiesAutoGenerated has a new required parameter build_version
• Operation ServiceUnitsOperations.list has a new signature
• Operation ServiceTopologiesOperations.delete has a new signature

1.0.0b1 (2020-11-30)

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-hypernode.com/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

• 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

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 for an overview.

0.2.0 (2019-12-31)

Features

• Added operation ServiceUnitsOperations.list
• Added operation RolloutsOperations.list
• Added operation ArtifactSourcesOperations.list
• Added operation ServiceTopologiesOperations.list
• Added operation StepsOperations.list
• Added operation ServicesOperations.list
• Added operation Operations.list

Breaking changes

• Parameter attributes of model WaitStepProperties is now required
• Removed operation Operations.get

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. DeploymentManagerClient cannot be imported from azure.mgmt.deploymentmanager.deployment_manager_client anymore (import from azure.mgmt.deploymentmanager works like before) DeploymentManagerClientConfiguration import has been moved from azure.mgmt.deploymentmanager.deployment_manager_client to azure.mgmt.deploymentmanager A model MyClass from a "models" sub-module cannot be imported anymore using azure.mgmt.deploymentmanager.models.my_class (import from azure.mgmt.deploymentmanager.models works like before) An operation class MyClassOperations from an operations sub-module cannot be imported anymore using azure.mgmt.deploymentmanager.operations.my_class_operations (import from azure.mgmt.deploymentmanager.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 (2019-04-15)

• Initial Release