[Hub Generated] Review request for Microsoft.LoadTestService to add version preview/2022-04-15-preview#20917
Merged
chunyu3 merged 4 commits intoAzure:mainfrom Sep 30, 2022
mjmadhu:dev-loadtestservice-Microsoft.LoadTestService-2022-04-15-preview
Merged
[Hub Generated] Review request for Microsoft.LoadTestService to add version preview/2022-04-15-preview#20917chunyu3 merged 4 commits intoAzure:mainfrom mjmadhu:dev-loadtestservice-Microsoft.LoadTestService-2022-04-15-preview
chunyu3 merged 4 commits intoAzure:mainfrom
mjmadhu:dev-loadtestservice-Microsoft.LoadTestService-2022-04-15-preview
Conversation
Swagger Validation Report
|
| compared swaggers (via Oad v0.9.7)] | new version | base version |
|---|---|---|
| loadtestservice.json | 2022-12-01(eedda8e) | 2022-04-15-preview(main) |
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
️⚠️LintDiff: 1 Warnings warning [Detail]
| compared tags (via openapi-validator v1.13.0) | new version | base version |
|---|---|---|
| package-2022-12-01 | package-2022-12-01(eedda8e) | default(main) |
[must fix]The following errors/warnings are introduced by current PR:
| Rule | Message | Related RPC [For API reviewers] |
|---|---|---|
| Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isAvailable Location: Microsoft.LoadTestService/stable/2022-12-01/loadtestservice.json#L798 |
️️✔️Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️❌ApiReadinessCheck: 1 Errors, 0 Warnings failed [Detail]
| Rule | Message |
|---|---|
API Readiness check failed. Please make sure your service is deployed. |
"code: InvalidResourceType, message: The resource type 'operations' could not be found in the namespace 'Microsoft.LoadTestService' for api version '2022-12-01'. The supported api-versions are '2020-09-01-preview, 2021-09-01-preview, 2021-11-01-preview, 2021-12-01-preview, 2022-04-01-preview, 2022-04-15-preview, 2022-08-01-preview'." |
️⚠️~[Staging] ServiceAPIReadinessTest: 0 Warnings warning [Detail]
API Test is not triggered due to precheck failure. Check pipeline log for details.
️⚠️~[Staging] TrafficValidation: 0 Warnings warning [Detail]
API Test is not triggered due to precheck failure. Check pipeline log for details.
️️✔️ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️PoliCheck succeeded [Detail] [Expand]
Validation passed for PoliCheck.
️⚠️SDK Track2 Validation: 1 Warnings warning [Detail]
- The following tags are being changed in this PR
- "https://github.com/Azure/azure-rest-api-specs/blob/eedda8e42be254e5f25f246f636b4101d0735544/specification/loadtestservice/resource-manager/readme.md#tag-package-2022-12-01">loadtestservice/resource-manager/readme.md#package-2022-12-01
| Rule | Message |
|---|---|
| "readme":"loadtestservice/resource-manager/readme.md", "tag":"package-2022-12-01", "details":"Security scheme azure_auth is unknown and will not be processed. Only supported types are AADToken, AzureKey, Anonymous" |
️️✔️PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
️️✔️CadlValidation succeeded [Detail] [Expand]
Validation passes for CadlValidation.
️️✔️PR Summary succeeded [Detail] [Expand]
Validation passes for Summary.
|
Hi, @mjmadhu 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. vscswagger@microsoft.com |
Swagger Generation Artifacts
|
Generated ApiView
|
|
Hi, @mjmadhu your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board(armapireview@microsoft.com). |
11 tasks
This was referenced Sep 28, 2022
This was referenced Sep 28, 2022
mentat9
reviewed
Sep 28, 2022
...estservice/resource-manager/Microsoft.LoadTestService/stable/2022-12-01/loadtestservice.json
Show resolved
Hide resolved
mentat9
reviewed
Sep 28, 2022
...estservice/resource-manager/Microsoft.LoadTestService/stable/2022-12-01/loadtestservice.json
Outdated
Show resolved
Hide resolved
mentat9
reviewed
Sep 28, 2022
...estservice/resource-manager/Microsoft.LoadTestService/stable/2022-12-01/loadtestservice.json
Outdated
Show resolved
Hide resolved
mentat9
reviewed
Sep 28, 2022
...estservice/resource-manager/Microsoft.LoadTestService/stable/2022-12-01/loadtestservice.json
Show resolved
Hide resolved
mentat9
reviewed
Sep 28, 2022
...estservice/resource-manager/Microsoft.LoadTestService/stable/2022-12-01/loadtestservice.json
Show resolved
Hide resolved
|
Please ensure to respond feedbacks from the ARM API reviewer. When you are ready to continue the ARM API review, please remove |
Updated description for outbound network dependency endpoints
Member
Author
|
@chunyu3 Please help with the merge of the PR |
chunyu3
approved these changes
Sep 30, 2022
This was referenced Sep 30, 2022
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
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.
This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
ARM API Information (Control Plane)
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.