[Azure Search] Remove the "track2" version of 2019-05-06-Preview swaggers #7734
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 |
|
Can one of the admins verify this patch? |
brjohnstmsft
approved these changes
Nov 7, 2019
sarangan12
approved these changes
Nov 12, 2019
solhaile
pushed a commit
to solhaile/azure-rest-api-specs
that referenced
this pull request
Nov 13, 2019
…gers (Azure#7734) * Remove from 'track2' copy the swagger for 2019-05-06-Preview * Remove from 'track2' copy the swagger for 2019-05-06-Preview for the service swagger
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR #7615 introduced (as a work in progress) swagger for the REST API version
2019-05-06-PreviewIt was introduced in the carved out "track1" directory as well as the non-carved out "track2" (base) directory - we expected work on both to happen in parallel.
However, the Azure search is now ready to add features (and finish the progress) for "track1"
2019-05-06-Preview; and we don't have plans on "track2" until next year - meaning, if we keep both copies around, we'll be required to duplicate changes unnecessarily.This PR eliminates the "track2" copy in the hopes that in the future when are ready to work on it, a different PR will introduce it.
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:
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.