4.0.0 (2021-06-22)
Changed
- Key Vault API version 7.2 is now the default
KeyVaultAccessControlClient.delete_role_assignment
and
.delete_role_definition
no longer raise an error when the resource to be
deleted is not found- Raised minimum azure-core version to 1.11.0
Added
KeyVaultAccessControlClient.set_role_definition
accepts an optional
assignable_scopes
keyword-only argument
Breaking Changes
KeyVaultAccessControlClient.delete_role_assignment
and
.delete_role_definition
return None- Changed parameter order in
KeyVaultAccessControlClient.set_role_definition
.
permissions
is now an optional keyword-only argument - Renamed
BackupOperation
toKeyVaultBackupResult
, and removed all but
itsfolder_url
property - Removed
RestoreOperation
andSelectiveKeyRestoreOperation
classes - Removed
KeyVaultBackupClient.begin_selective_restore
. To restore a
single key, pass the key's name toKeyVaultBackupClient.begin_restore
:# before (4.0.0b3): client.begin_selective_restore(folder_url, sas_token, key_name) # after: client.begin_restore(folder_url, sas_token, key_name=key_name)
- Removed
KeyVaultBackupClient.get_backup_status
and.get_restore_status
. Use
the pollers returned byKeyVaultBackupClient.begin_backup
and.begin_restore
to check whether an operation has completed KeyVaultRoleAssignment
'sprincipal_id
,role_definition_id
, andscope
are now properties of aproperties
property# before (4.0.0b3): print(KeyVaultRoleAssignment.scope) # after: print(KeyVaultRoleAssignment.properties.scope)
- Renamed
KeyVaultPermission
properties:allowed_actions
->actions
denied_actions
->not_actions
allowed_data_actions
->data_actions
denied_data_actions
->denied_data_actions
- Renamed argument
role_assignment_name
toname
in
KeyVaultAccessControlClient.create_role_assignment
,.delete_role_assignment
,
and.get_role_assignment
- Renamed argument
role_definition_name
toname
in
KeyVaultAccessControlClient.delete_role_definition
and.get_role_definition
- Renamed argument
role_scope
toscope
inKeyVaultAccessControlClient
methods