Microsoft Azure Key Vault Management Client Library for Python
Microsoft Azure SDK for Python
This is the Microsoft Azure Key Vault Management Client Library.
Azure Resource Manager (ARM) is the next generation of management APIs that replace the old Azure Service Management (ASM).
This package has been tested with Python 2.7, 3.4, 3.5, 3.6 and 3.7.
For the older Azure Service Management (ASM) libraries, see azure-servicemanagement-legacy library.
For a more complete set of Azure libraries, see the azure bundle package.
For code examples, see Key Vault Management on docs.microsoft.com.
If you encounter any bugs or have suggestions, please file an issue in the Issues section of the project.
General Breaking changes
This version uses a next-generation code generator that might introduce breaking changes if you were importing from the v20xx_yy_zz API folders. 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.
- KeyVaultManagementClient cannot be imported from azure.mgmt.key_vault.v20xx_yy_zz.key_vault_management_client anymore (import from azure.mgmt.key_vault.v20xx_yy_zz works like before)
- KeyVaultManagementClientConfiguration import has been moved from azure.mgmt.key_vault.v20xx_yy_zz.key_vault_management_client to azure.mgmt.key_vault.v20xx_yy_zz
- A model MyClass from a “models” sub-module cannot be imported anymore using azure.mgmt.key_vault.v20xx_yy_zz.models.my_class (import from azure.mgmt.key_vault.v20xx_yy_zz.models works like before)
- An operation class MyClassOperations from an operations sub-module cannot be imported anymore using azure.mgmt.key_vault.v20xx_yy_zz.operations.my_class_operations (import from azure.mgmt.key_vault.v20xx_yy_zz.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.
- Adding support for multi-api and API profiles
- Moving azure-mgmt-keyvault to stable API version 2018-02-14
- Upgraded to autorest 3.0 generated code
General Breaking changes
This version uses a next-generation code generator that might introduce breaking changes.
- Model signatures now use only keyword-argument syntax. All positional arguments must be re-written as keyword-arguments. To keep auto-completion in most cases, models are now generated for Python 2 and Python 3. Python 3 uses the “*” syntax for keyword-only arguments.
- Enum types now use the “str” mixin (class AzureEnum(str, Enum)) to improve the behavior when unrecognized enum values are encountered.
While this is not a breaking change, the distinctions are important, and are documented here:
At a glance:
- “is” should not be used at all.
- “format” will return the string value, where “%s” string formatting will return NameOfEnum.stringvalue. Format syntax should be prefered.
- New Long Running Operation:
- Return type changes from msrestazure.azure_operation.AzureOperationPoller to msrest.polling.LROPoller. External API is the same.
- Return type is now always a msrest.polling.LROPoller, regardless of the optional parameters used.
- The behavior has changed when using raw=True. Instead of returning the initial call result as ClientRawResponse, without polling, now this returns an LROPoller. After polling, the final resource will be returned as a ClientRawResponse.
- New polling parameter. The default behavior is Polling=True which will poll using ARM algorithm. When Polling=False, the response of the initial call will be returned without polling.
- polling parameter accepts instances of subclasses of msrest.polling.PollingMethod.
- add_done_callback will no longer raise if called after polling is finished, but will instead execute the callback right away.
- Upgrading to API version 2018-02-14-preview
- Breaking change in vault create_or_update now returns a ‘LROPoller’ objects rather than the Vault, to allow callers to determine when the vault is ready to accept traffic. Callers should use the result() method to block until the vault is accessible.
- Adding network_acls vault property for limiting network access to a vault
- Adding managed storage account key backup, restore and soft delete support
- Adding vault property enable_purge_protection for enhance protection against vault deletion
- upgrading to API version 2016-10-01
- adding keyvault management plane updates to enable the soft delete feature for a new or existing keyvault
- this contains a backwards breaking change removing the All value from KeyPermissions, SecretPermissions and CertificatePermissions
- Fix possible deserialization error, but updating from list<enumtype> to list<str> when applicable
- This wheel package is now built with the azure wheel extension
- Fix list Vault by subscription method return type
- Initial preview release (API Version 2016-10-02)
Release history Release notifications | RSS feed
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
|Filename, size||File type||Python version||Upload date||Hashes|
|Filename, size azure_mgmt_keyvault-2.0.0-py2.py3-none-any.whl (80.3 kB)||File type Wheel||Python version py2.py3||Upload date||Hashes View|
|Filename, size azure-mgmt-keyvault-2.0.0.zip (96.0 kB)||File type Source||Python version None||Upload date||Hashes View|
Hashes for azure_mgmt_keyvault-2.0.0-py2.py3-none-any.whl