Support.json Get Support Ticket serviceId + ProbClassId filter changes#19117
Conversation
|
Hi, @devinlstoen 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 |
|---|---|
R4018 - OperationsApiResponseSchema |
The response schema of operations API '/providers/Microsoft.Support/operations' does not match the ARM specification. Please standardize the schema. Location: Microsoft.Support/stable/2020-04-01/support.json#L37 |
R4037 - MissingTypeObject |
The schema 'OperationsListResult' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Support/stable/2020-04-01/support.json#L789 |
R4037 - MissingTypeObject |
The schema 'display' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Support/stable/2020-04-01/support.json#L813 |
| Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: nameAvailable Location: Microsoft.Support/stable/2020-04-01/support.json#L975 |
|
| Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: require24X7Response Location: Microsoft.Support/stable/2020-04-01/support.json#L1182 |
️️✔️Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️ApiReadinessCheck succeeded [Detail] [Expand]
️️✔️ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️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.
️❌PoliCheck: 0 Errors, 0 Warnings failed [Detail]
️️✔️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
|
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Hi @devinlstoen, Your PR has some issues. Please fix the CI sequentially by following the order of
|
1 similar comment
|
Hi @devinlstoen, Your PR has some issues. Please fix the CI sequentially by following the order of
|
|
@devinlstoen Please address the Avocado and PrettierCheck error. |
Hello, I addressed the Avocado and PrettierCheck errors. |
I have a question about the filter parameters. Should I include the entire problem classification id ("/providers/Microsoft.Support/services/service_guid/problemClassifications/compute_vm_problemClassification_guid",) and service id ("/providers/Microsoft.Support/services/vm_windows_service_guid/problemClassifications/problemClassification_guid") in the filter request? Or am I fine just requiring the guid? (i.e "$filter": "ProblemClassificationId eq 'compute_vm_problemClassification_guid'") |
for the list operation, filter is ok. |
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
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 appy 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 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.