mgmt powerapps test #22201
Draft
mgmt powerapps test #22201
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi, @dw511214992 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. [email protected] |
Swagger Validation Report
|
| Rule | Message |
|---|---|
|
The default tag should contain all APIs. The API path /subscriptions/{}/providers/Microsoft.DataBoxEdge/skus is not in the default tag. Please make sure the missing API swaggers are in the default tag.readme: specification/sdkreleaseplannertest/resource-manager/readme.md json: Microsoft.DataBoxEdge/stable/2019-08-01/databoxedge.json |
️️✔️ApiReadinessCheck succeeded [Detail] [Expand]
️⚠️~[Staging] ServiceAPIReadinessTest: 0 Warnings warning [Detail]
API Test is not triggered due to precheck failure. Check pipeline log for details.
️️✔️~[Staging] SwaggerAPIView succeeded [Detail] [Expand]
️️✔️~[Staging] CadlAPIView succeeded [Detail] [Expand]
️❌ModelValidation: 696 Errors, 0 Warnings failed [Detail]
Only 30 items are listed, please refer to log for more details.
️️✔️SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️PoliCheck succeeded [Detail] [Expand]
Validation passed for PoliCheck.
️️✔️PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️❌SpellCheck: 7 Errors, 0 Warnings failed [Detail]
| Rule | Message |
|---|---|
|
Unknown word (Fulfilment), please fix the error or add words to ./custom-words.txt path: Microsoft.DataBoxEdge/preview/2020-05-01-preview/databoxedge.json#L5180:22 |
|
Unknown word (Fulfilment), please fix the error or add words to ./custom-words.txt path: Microsoft.DataBoxEdge/preview/2020-09-01-preview/databoxedge.json#L7007:22 |
|
Unknown word (Fulfilment), please fix the error or add words to ./custom-words.txt path: Microsoft.DataBoxEdge/stable/2019-03-01/databoxedge.json#L4098:22 |
|
Unknown word (Fulfilment), please fix the error or add words to ./custom-words.txt path: Microsoft.DataBoxEdge/stable/2019-07-01/databoxedge.json#L4241:22 |
|
Unknown word (Fulfilment), please fix the error or add words to ./custom-words.txt path: Microsoft.DataBoxEdge/stable/2019-08-01/databoxedge.json#L4907:22 |
|
Unknown word (Fulfilment), please fix the error or add words to ./custom-words.txt path: Microsoft.DataBoxEdge/stable/2020-09-01/databoxedge.json#L7007:22 |
|
Unknown word (Fulfilment), please fix the error or add words to ./custom-words.txt path: Microsoft.DataBoxEdge/stable/2020-12-01/databoxedge.json#L7088:22 |
️️✔️Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
️️✔️CadlValidation succeeded [Detail] [Expand]
Validation passes for CadlValidation.
️❌PR Summary: 0 Errors, 0 Warnings failed [Detail]
Swagger Generation Artifacts
|
Generated ApiView
|
|
Hi, @dw511214992, For review efficiency consideration, when creating a new api version, it is required to place API specs of the base version in the first commit, and push new version updates into successive commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki. Or you could onboard API spec pipeline |
|
Hi @dw511214992 This PR was flagged for introducing a new RP namespace that is not being onboarded with RPaaS. Merging this PR to the main branch will be blocked as RPaaS is required for new RPs. To resolve this and allow the PR to be merged into the main branch, please use RPaaS to onboard the new RP. |
This was referenced Jan 16, 2023
Closed
Closed
zzvswxy
added
Approved-OkToMerge
This was referenced Jan 16, 2023
This was referenced Jan 17, 2023
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ARM API Information (Control Plane)
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo. If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:
Contribution checklist (MS Employees Only):
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Otherwise your PR may be subject to ARM review requirements. Complete the following:
Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review. Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.
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 you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.