Add custom speech apis#13013
Add custom speech apis#13013anuchandy merged 35 commits intoAzure:masterfrom bexxx:bexxx/addCustomSpeechApis
Conversation
|
Hi, @bexxx 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 |
|
In the Window Period to fix mismatches between swagger and service, when PR is labelled with “FixS360”, breaking change can be approved by PR assignee; the Azure Breaking Change Board is no longer required to approve the PR. Please ensure to clarify what s360 action items to be solved, and @ mention PR assignee for awareness. Please check this wiki Window to Fix Broken for more details. |
Swagger Validation Report
|
| Rule | Message |
|---|---|
| Consider using x-ms-client-flatten to provide a better end user experience Location: SpeechToText/stable/v2.0/speechtotext.json#L4905 |
|
| Consider using x-ms-client-flatten to provide a better end user experience Location: SpeechToText/stable/v2.0/speechtotext.json#L5091 |
|
| Consider using x-ms-client-flatten to provide a better end user experience Location: SpeechToText/stable/v2.0/speechtotext.json#L5318 |
|
| Consider using x-ms-client-flatten to provide a better end user experience Location: SpeechToText/stable/v2.0/speechtotext.json#L5444 |
|
| Consider using x-ms-client-flatten to provide a better end user experience Location: SpeechToText/stable/v2.0/speechtotext.json#L5501 |
|
| Consider using x-ms-client-flatten to provide a better end user experience Location: SpeechToText/stable/v2.0/speechtotext.json#L5584 |
|
| Consider using x-ms-client-flatten to provide a better end user experience Location: SpeechToText/stable/v2.0/speechtotext.json#L5619 |
|
| Consider using x-ms-client-flatten to provide a better end user experience Location: SpeechToText/stable/v2.0/speechtotext.json#L5726 |
|
| Consider using x-ms-client-flatten to provide a better end user experience Location: SpeechToText/stable/v2.0/speechtotext.json#L5766 |
|
| Consider using x-ms-client-flatten to provide a better end user experience Location: SpeechToText/stable/v3.0/speechtotext.json#L6218 |
️️✔️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.
️⚠️[Staging] SDK Track2 Validation: 2 Warnings warning [Detail]
- The following tags are being changed in this PR
| Rule | Message |
|---|---|
| "readme":"cognitiveservices/data-plane/Speech/SpeechToText/readme.md", "tag":"release_2_0", "details":"Checking for duplicate schemas, this could take a (long) while. Run with --verbose for more detail." |
|
| "readme":"cognitiveservices/data-plane/Speech/SpeechToText/readme.md", "tag":"release_3_0", "details":"Checking for duplicate schemas, this could take a (long) while. Run with --verbose for more detail." |
️️✔️[Staging] PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️[Staging] SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
|
Swagger pipeline restarted successfully, please wait for status update in this comment. |
|
Hi @bexxx, Your PR has some issues. Please fix the CI sequentially by following the order of
|
|
@anuchandy This is an existing service (both versions are GA, v2 is now on the deprecation train) and we've been asked to publish the swaggers in this repo. The checks are green now. Please start reviewing the changes. Thanks! |
|
@anuchandy This PR is final from our side. Please merge in when possible. Thanks a lot! |
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 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.