4.2.0 (2020-08-11)
Fixed
- Values of
x-ms-keyvault-region
andx-ms-keyvault-service-version
headers
are no longer redacted in logging output CryptographyClient
will no longer perform encrypt or wrap operations when
its key has expired or is not yet valid
Changed
- Key Vault API version 7.1 is now the default
- Updated minimum
azure-core
version to 1.7.0
Added
- At construction, clients accept a
CustomHookPolicy
through the optional
keyword argumentcustom_hook_policy
- All client requests include a unique ID in the header
x-ms-client-request-id
- Dependency on
azure-common
for multiapi support