-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Model role scope, permissions, and role type as enum values #12414
Conversation
Hi, @christothes Thanks for your PR. I am workflow bot for review process. Here are some small tips. Any feedback about review process or workflow bot, pls contact swagger and tools team. vsswagger@microsoft.com |
Swagger Validation Report
|
Rule | Message |
---|---|
REQUIRED_PARAMETER_EXAMPLE_NOT_FOUND |
In operation "RoleDefinitions_Delete", parameter scope is required in the swagger spec but is not present in the provided example parameter values. Url: Microsoft.KeyVault/preview/7.2-preview/rbac.json#L38 |
REQUIRED_PARAMETER_EXAMPLE_NOT_FOUND |
In operation "RoleDefinitions_Get", parameter scope is required in the swagger spec but is not present in the provided example parameter values. Url: Microsoft.KeyVault/preview/7.2-preview/rbac.json#L139 |
️️✔️
SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️
[Staging] Cross Version BreakingChange (Base on preview version) succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️
[Staging] Cross Version BreakingChange (Base on stable version) succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️
CredScan succeeded [Detail] [Expand]
There is no credential detected.
Swagger Generation Artifacts
|
Hi @christothes, Your PR has some issues. Please fix the CI sequentially by following the order of
|
|
specification/keyvault/data-plane/Microsoft.KeyVault/preview/7.2-preview/rbac.json
Outdated
Show resolved
Hide resolved
….2-preview/rbac.json Co-authored-by: David Desberg <david@daviddesberg.com>
The model validation failures are being addressed in a separate PR, and we don't need to block on the Go SDK build error. @ArcturusZhang do you know what this Go SDK failure means? It's unclear from the log. |
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
Hi @jhendrixMSFT the failure has been fixed which is caused by some bugs in the pipeline itself. |
"description": "Backup HSM keys." | ||
}, | ||
{ | ||
"name": "RestoreHsmKey", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be RestoreHsmKeys
to align with BackupHsmKeys
?
] | ||
} | ||
}, | ||
"DataActionPermission": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another naming question: should this be changed to DataAction
since it'll be prefixed with "KeyVault" in the SDK (and they describe action permissions in the same way KeyOperation
describes operation permissions)?
@christothes any other pending changes or is this ready for merge? |
Should be ready - thanks! |
) * define permissions enums * anyOf * fixup schema * add enums for roleType and roleDefinitionType * add roleScope enum * scope names * set name for enum * consolidate DataActions * revert consolidation * enum names and desscriptions * fix ReadDeletedHsmKey * ReadHsmSecurityDomainTransferKey * spellcheck * pr comments * renames and description changes * Update specification/keyvault/data-plane/Microsoft.KeyVault/preview/7.2-preview/rbac.json Co-authored-by: David Desberg <david@daviddesberg.com> * renames Co-authored-by: David Desberg <david@daviddesberg.com>
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Changelog
Please ensure to add changelog with this PR by answering the following questions.
Contribution checklist:
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.
Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.
If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.