[Key Vault] Address administration feedback#19099
Conversation
|
This pull request is protected by Check Enforcer. What is Check Enforcer?Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass. Why am I getting this message?You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged. What should I do now?If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows: What if I am onboarding a new service?Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment: |
| :type role_scope: str or KeyVaultRoleScope | ||
| :param role_definition_name: the unique role definition name. Unless a UUID is provided, a new role definition | ||
| :type scope: str or KeyVaultRoleScope | ||
| :keyword definition_name: the unique role definition name. Unless a UUID is provided, a new role definition |
There was a problem hiding this comment.
I wonder if we should shorten this to name, since it would align with the UUID name of a role assignment in create_role_assignment, and match the name argument in get_role_definition and delete_role_definition. I initially thought we should keep definition_ to differentiate it from role_name but a plain name in this context sort of implies a definition_ prefix
There was a problem hiding this comment.
Seems reasonable to me, let's give it a try.
| self._name = kwargs.get("name") | ||
| self._properties = kwargs.get("properties") | ||
| self._type = kwargs.get("assignment_type") | ||
| self.name = kwargs.get("name") |
There was a problem hiding this comment.
Is there a particular reason to move away from properties?
There was a problem hiding this comment.
Co-authored-by: McCoy Patiño <39780829+mccoyp@users.noreply.github.com>
mccoyp
left a comment
There was a problem hiding this comment.
Looks good! I think we need to also override a frozen requirement to get CI passing: https://dev.azure.com/azure-sdk/public/_build/results?buildId=942747&view=logs&j=b70e5e73-bbb6-5567-0939-8415943fadb9&t=b64fce29-1009-5e76-50fb-7b596c2db4c3&l=2026
| and `.get_role_assignment` | ||
| - Renamed argument `role_definition_name` to `name` in | ||
| `KeyVaultAccessControlClient.delete_role_definition` and `.get_role_definition` | ||
|
|
There was a problem hiding this comment.
We'll want to mention other argument renames too, like role_scope -> scope in multiple methods
…into protocol_base * 'master' of https://github.com/Azure/azure-sdk-for-python: (229 commits) Sync eng/common directory with azure-sdk-tools for PR 1688 (#19272) update all ubuntu vmImage to 20.04 (#19227) add base class for feedback (#19265) Enable tests for integration samples (#18531) docs: fix a few simple typos (#19127) Increment package version after release of azure-eventgrid (#19197) Increment package version after release of azure-monitor-query (#19208) earliest versions of communication identity tests are set up improperly. skip 1.0.0 in regression testing (#19258) Run mypy in azure-keyvault-administration CI (#19246) [text analytics] change return type of analyze actions to list of list (#18994) Increment package version after release of azure-data-tables (#19192) suppress min number less than 14 (#19230) [Key Vault] Address administration feedback (#19099) [textanalytics] remove warning tests (#19217) [translation] enable samples to run in CI (#19190) update custom_granularity_value to be more than 300 (#19215) Increment package version after release of azure-security-attestation (#19212) Enabling Before/After Test Customization for Standard CI Pipelines (#19187) bump sphinx version to resolve the weird issue with the caption not getting the correct class (#19188) [AutoRelease] t2-agrifood-2021-06-09-15946 (#19174) ...
Summarizing changes:
begin_selective_key_restoreintobegin_restore, former gains akey_namekwargbegin_restorepoller result is None, i.e. no longer a modelget_backup_status,get_restore_statusKeyVaultRestoreOperation,KeyVaultSelectiveKeyRestoreOperationKeyVaultBackupOperationreduced to one property,folder_urlcreate_role_assignment(assignment_name=...)->create_role_assignment(name=...)Closes #19123