Adding indexing parameters to the swagger for Cognitive Search#10349
Adding indexing parameters to the swagger for Cognitive Search#10349lmazuel merged 48 commits intoAzure:masterfrom
Conversation
… V2 SDK. These weren't referenced in the examples.
…to false for failOn* properties, and removed en-us locale from URL
Add swagger spec for indexer execution environment
…ermarsman/azure-rest-api-specs into jennmar/indexerParameters
Add swagger spec for indexer execution environment in 2 new API versions
azure-sdk-for-java - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
Trenton Generation - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
azure-sdk-for-python - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
azure-sdk-for-js - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
azure-sdk-for-go - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
azure-sdk-for-python-track2 - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
Azure CLI Extension Generation - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
This PR should replace #9900. |
|
The remaining BreakingChange errors are for "1034 - AddedRequiredProperty", but the properties added are all optional in a Configuration property bag. |
specification/search/data-plane/Azure.Search/preview/2020-06-30-Preview/searchservice.json
Outdated
Show resolved
Hide resolved
specification/search/data-plane/Azure.Search/preview/2020-06-30-Preview/searchservice.json
Outdated
Show resolved
Hide resolved
|
Azure Pipelines successfully started running 1 pipeline(s). |
azure-resource-manager-schemas - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
| } | ||
| }, | ||
| "description": "Represents parameters for indexer execution." | ||
| "description": "Represents parameters for indexer execution.", |
There was a problem hiding this comment.
Actually line 5790, but GitHub won't let me comment on surrounding code 😣: add a $ref to this model from configuration.
There was a problem hiding this comment.
Oh sorry, I thought you wanted them completely decoupled by leaving the configuration's type as object.
There was a problem hiding this comment.
This will be a breaking change then, no?
|
Azure Pipelines successfully started running 1 pipeline(s). |
heaths
left a comment
There was a problem hiding this comment.
Looks good, as long as it doesn't generating any breaking change warnings with the service implementation.
specification/search/data-plane/Azure.Search/preview/2020-06-30-Preview/searchservice.json
Show resolved
Hide resolved
@heaths it looks like this is generating Breaking Change warnings. Specifically, lots of added required properties. |
|
@tjprescott, I don't see any of the newly added properties being required. But it is Monday. Am I missing something? |
True, I don't see any of them marked required, and they all seem to have defaults. @johanste who would be the right person to investigate this from the tooling side? |
|
@tjprescott, the openapihub has a teams support channel. I'd start there. |
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
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.
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 API Review Board as defined in the Breaking Change Policy.
Please follow the link to find more details on PR review process.