Skip to content

[Azure Search] Introduce a few breaking changes in swagger specifications#6934

Merged
yungezz merged 5 commits intoAzure:masterfrom
arv100kri:arv100kri/skillset-breaking-changes
Aug 21, 2019
Merged

[Azure Search] Introduce a few breaking changes in swagger specifications#6934
yungezz merged 5 commits intoAzure:masterfrom
arv100kri:arv100kri/skillset-breaking-changes

Conversation

@arv100kri
Copy link
Member

@arv100kri arv100kri commented Aug 12, 2019

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)

  • Skills can now optionally take in a name property
  • WebApiSkill has an optional degreeOfParallelism property, which can allow customers to specify how many API calls (if non-null, non-zero) can be made in parallel to their endpoint
  • Add more information to indexer execution's errors and warnings

Latest 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:

  • I have reviewed the documentation for the workflow.
  • Validation tools were run on swagger spec(s) and have all been fixed in this PR.
  • The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

  • Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
  • adding/removing APIs.
  • adding/removing properties.
  • adding/removing API-version.
  • adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

  • If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
    Please follow the link to find more details on API review process.

@arv100kri arv100kri requested a review from brjohnstmsft August 12, 2019 21:01
@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Aug 12, 2019

In Testing, Please Ignore

[Logs] (Generated from 3d983e6, Iteration 5)

No readme.md specification configuration files were found that are associated with the files modified in this pull request.

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@arv100kri arv100kri marked this pull request as ready for review August 12, 2019 21:01
@AutorestCI
Copy link

AutorestCI commented Aug 12, 2019

Automation for azure-sdk-for-go

Nothing to generate for azure-sdk-for-go

@AutorestCI
Copy link

AutorestCI commented Aug 12, 2019

Automation for azure-sdk-for-python

Nothing to generate for azure-sdk-for-python

@brjohnstmsft
Copy link
Member

@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).

@arv100kri
Copy link
Member Author

@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

@arv100kri arv100kri requested a review from brjohnstmsft August 16, 2019 01:33
@bsiegel bsiegel removed the Reassign label Aug 19, 2019
@yaohaizh yaohaizh added the APIStewardshipBoard-ReviewRequested This should be reviewed by the Azure API Stewardship team in partnership with the service team. label Aug 20, 2019
@yaohaizh
Copy link
Contributor

@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.

@brjohnstmsft
Copy link
Member

@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?

@yaohaizh
Copy link
Contributor

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.

@yungezz
Copy link
Member

yungezz commented Aug 21, 2019

checked with @yaohaizh, this PR is ready for merge. ModelValidation error is an known issue.

@yungezz yungezz merged commit ea2dbe5 into Azure:master Aug 21, 2019
@yaohaizh yaohaizh removed the APIStewardshipBoard-ReviewRequested This should be reviewed by the Azure API Stewardship team in partnership with the service team. label Aug 21, 2019
leniatgh pushed a commit to leniatgh/azure-rest-api-specs that referenced this pull request May 13, 2022
* 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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants