[Azure Search] Introduce a few breaking changes in swagger specifications#6934
Conversation
|
Can one of the admins verify this patch? |
Automation for azure-sdk-for-goNothing to generate for azure-sdk-for-go |
Automation for azure-sdk-for-pythonNothing to generate for azure-sdk-for-python |
...oft.Azure.Search.Service/stable/2019-05-06/examples/SearchServiceCreateOrUpdateSkillset.json
Show resolved
Hide resolved
...Microsoft.Azure.Search.Service/stable/2019-05-06/examples/SearchServiceGetIndexerStatus.json
Outdated
Show resolved
Hide resolved
...ne/Microsoft.Azure.Search.Service/stable/2019-05-06/examples/SearchServiceListSkillsets.json
Show resolved
Hide resolved
|
@arv100kri Please ensure that the example changes pass validation (not sure at a glance that they're failing validation because there are other known issues with validating our Swagger right now). |
It's the same "base" set of validations errors for the various enum types |
...cation/search/data-plane/Microsoft.Azure.Search.Service/stable/2019-05-06/searchservice.json
Show resolved
Hide resolved
|
@arv100kri The model validation failed with https://dev.azure.com/azure-sdk/public/_build/results?buildId=90022&view=logs&j=8d2f9c49-cd83-5a9d-f3fe-2fd651afa742&t=43324f1f-6724-5d61-785f-f0ac9fd256a1&l=272 Please help fix it. Meanwhile, we need Azure API board review this. Thanks. |
|
@yaohaizh Those validation failures are the result of a known issue. See this for context: #5665 (comment) Regarding Azure API review board -- This PR is a change that brings our Swagger in line with the API that's actually deployed in production. Is a review still required in this case? |
|
As talked with @brjohnstmsft , the change is already deployed and the change reflect the service deployed. Given this, @yungezz , could you help merge this since it is blocked by model validation. |
|
checked with @yaohaizh, this PR is ready for merge. ModelValidation error is an known issue. |
* 2020-12-01-preview * readme * validation fixes * PR fixes * fixes * fixes * fixes * fixes * try fix warnings * PR comments * PR comments * PR comments * PR comments * rename Microsoft.Portal to Microsoft.PortalServices * rename Microsoft.Portal to Microsoft.PortalServices * linting * fix lint Co-authored-by: Ryan Benson <rbenson@microsoft.com>
This PR attempts at bringing the swagger spec in line with the REST API behavior, which intentionally introduces a few breaking changes (which will follow in a subsequent major version SDK update)
namepropertydegreeOfParallelismproperty, which can allow customers to specify how many API calls (if non-null, non-zero) can be made in parallel to their endpointLatest improvements:
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Contribution checklist:
ARM API Review Checklist
Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.
Please follow the link to find more details on API review process.