[Hub Generated] Review request for Microsoft.CostManagement to add version stable/2021-10-01 #18190
Conversation
This file contains 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, @mitagarg 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 Validation Report
|
| Rule | Message |
|---|---|
| Since operation 'Dimensions_ByExternalCloudProviderType' response has model definition 'x-ms-pageable', it should be of the form '_list'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: Microsoft.CostManagement/stable/2021-10-01/costmanagement.json#L876 |
|
| 'GET' operation 'Dimensions_ByExternalCloudProviderType' should use method name 'Get' or Method name start with 'List'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: Microsoft.CostManagement/stable/2021-10-01/costmanagement.json#L876 |
|
| 'PATCH' operation 'Alerts_Dismiss' should use method name 'Update'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: Microsoft.CostManagement/stable/2021-10-01/costmanagement.json#L487 |
|
| Based on the response model schema, operation 'Alerts_List' might be pageable. Consider adding the x-ms-pageable extension. Location: Microsoft.CostManagement/stable/2021-10-01/costmanagement.json#L383 |
|
| Based on the response model schema, operation 'Alerts_ListExternal' might be pageable. Consider adding the x-ms-pageable extension. Location: Microsoft.CostManagement/stable/2021-10-01/costmanagement.json#L537 |
|
| OperationId should contain the verb: 'forecast' in:'Forecast_Usage'. Consider updating the operationId Location: Microsoft.CostManagement/stable/2021-10-01/costmanagement.json#L586 |
|
| OperationId should contain the verb: 'forecast' in:'Forecast_ExternalCloudProviderUsage'. Consider updating the operationId Location: Microsoft.CostManagement/stable/2021-10-01/costmanagement.json#L662 |
|
| OperationId should contain the verb: 'query' in:'Query_Usage'. Consider updating the operationId Location: Microsoft.CostManagement/stable/2021-10-01/costmanagement.json#L955 |
|
| OperationId should contain the verb: 'query' in:'Query_UsageByExternalCloudProviderType'. Consider updating the operationId Location: Microsoft.CostManagement/stable/2021-10-01/costmanagement.json#L1063 |
|
| OperationId should contain the verb: 'generatereservationdetailsreport' in:'GenerateReservationDetailsReport_ByBillingAccountId'. Consider updating the operationId Location: Microsoft.CostManagement/stable/2021-10-01/costmanagement.json#L1117 |
|
| OperationId should contain the verb: 'generatereservationdetailsreport' in:'GenerateReservationDetailsReport_ByBillingProfileId'. Consider updating the operationId Location: Microsoft.CostManagement/stable/2021-10-01/costmanagement.json#L1180 |
|
| Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: includeMonetaryCommitment Location: Microsoft.CostManagement/stable/2021-10-01/costmanagement.json#L1311 |
|
| The resource 'Dimension' does not have get operation, please add it. Location: Microsoft.CostManagement/stable/2021-10-01/costmanagement.json#L1853 |
|
| Do not have duplicate name of x-ms-example, make sure every x-ms-example name unique. Duplicate x-ms-example: ReservationDetails Location: Microsoft.CostManagement/stable/2021-10-01/costmanagement.json#L1185 |
️️✔️Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️~[Staging] ApiReadinessCheck succeeded [Detail] [Expand]
️❌ModelValidation: 1 Errors, 0 Warnings failed [Detail]
| Rule | Message |
|---|---|
|
x-ms-example not found in Operations_List. Url: Microsoft.CostManagement/stable/2021-10-01/costmanagement.json#L1242:14 |
️️✔️SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️Cross-Version Breaking Changes succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
️️✔️SDK Track2 Validation succeeded [Detail] [Expand]
Validation passes for SDKTrack2Validation
- The following tags are being changed in this PR
️️✔️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).
Swagger Generation Artifacts
|
|
[Call for Action] To better understand Azure service dev/test scenario, and support Azure service developer better on Swagger and REST API related tests in early phase, please help to fill in with this survey https://aka.ms/SurveyForEarlyPhase. It will take 5 to 10 minutes. If you already complete survey, please neglect this comment. Thanks. |
|
Hi @mitagarg, Your PR has some issues. Please fix the CI sequentially by following the order of
|
|
@ArcturusZhang could you review the Go SDK breaking change ? |
JeffreyRichter
added
the
Approved-BreakingChange
jianyexi
approved these changes
Mar 15, 2022
This was referenced Mar 15, 2022
FredericHeem
pushed a commit
to grucloud/azure-rest-api-specs
that referenced
this pull request
May 16, 2022
Co-authored-by: Mita Garg <v-migarg@microsoft.com>
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.
Changelog
Add a changelog entry for 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
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 label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.
-[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. 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 any of the following scenarios apply to the PR, request approval from the Breaking Change 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.