-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
PIM API Specs #12526
PIM API Specs #12526
Conversation
Hi, @amanswaika 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 |
---|---|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isOrganizationDefault New: Microsoft.Authorization/preview/2020-10-01-preview/RoleManagementPolicy.json#L246 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isApprovalRequired New: Microsoft.Authorization/preview/2020-10-01-preview/RoleManagementPolicy.json#L368 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isApprovalRequiredForExtension New: Microsoft.Authorization/preview/2020-10-01-preview/RoleManagementPolicy.json#L372 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isRequestorJustificationRequired New: Microsoft.Authorization/preview/2020-10-01-preview/RoleManagementPolicy.json#L376 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isApproverJustificationRequired New: Microsoft.Authorization/preview/2020-10-01-preview/RoleManagementPolicy.json#L412 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isEscalationEnabled New: Microsoft.Authorization/preview/2020-10-01-preview/RoleManagementPolicy.json#L428 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isBackup New: Microsoft.Authorization/preview/2020-10-01-preview/RoleManagementPolicy.json#L453 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isBackup New: Microsoft.Authorization/preview/2020-10-01-preview/RoleManagementPolicy.json#L490 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isEnabled New: Microsoft.Authorization/preview/2020-10-01-preview/RoleManagementPolicy.json#L517 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isExpirationRequired New: Microsoft.Authorization/preview/2020-10-01-preview/RoleManagementPolicy.json#L578 |
️️✔️
Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️
ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️
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, @amanswaika your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board(armapireview@microsoft.com). cc @yungezz |
Link to the approved private repo PR - https://github.com/Azure/azure-rest-api-specs-pr/pull/2049/ |
Hi @amanswaika, Your PR has some issues. Please fix the CI sequentially by following the order of
|
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
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.
Only a change in resource type name from an approved private PR
* PIM API Specs * update readme * Update * Update readme * operation id fix * name fix * Name changes * fix * Fix Co-authored-by: Aman Swaika <amansw@microsoft.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.