Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Search] Rename CognitiveServices to CognitiveServicesAccount #7859

Merged
merged 1 commit into from
Dec 10, 2019

Conversation

brjohnstmsft
Copy link
Member

Renaming some types and properties in the client programming model for Cognitive Search per Azure API Review Board feedback. This change is for Track 2 only to avoid breaking backwards compatibility of shipping SDKs (our first Track 2 SDK has not shipped yet).

FYI @arv100kri @sarangan12

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.

@AutorestCI
Copy link

AutorestCI commented Nov 28, 2019

Automation for azure-sdk-for-go

Nothing to generate for azure-sdk-for-go

@AutorestCI
Copy link

AutorestCI commented Nov 28, 2019

Automation for azure-sdk-for-python

Nothing to generate for azure-sdk-for-python

@brjohnstmsft
Copy link
Member Author

@sarangan12 This is blocking development of our Java SDK -- can you please review soon?

@jhendrixMSFT
Copy link
Member

@brjohnstmsft looks like a breaking change in a spec marked as stable, is this expected?

@brjohnstmsft
Copy link
Member Author

@jhendrixMSFT It is expected. This spec is probably in the wrong directory now. Here's what happened:

  • The specs in stable used to be only for our .NET SDK (Track 1).
  • We started work on a Track 2 Java SDK.
  • At some point, the specs needed to diverge, so we copied the specs into a "track1" folder that is used to maintain the .NET SDK.
  • As of now, the Java SDK hasn't been released yet, so making breaking changes here is expected, and fortunately not really breaking.

I hope this makes sense. Please let me know if you have any questions or concerns.

@brjohnstmsft
Copy link
Member Author

Also, there will be more changes like this coming as we address feedback from the Azure API Review Board.

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Dec 10, 2019

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

@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Dec 10, 2019

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

@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Dec 10, 2019

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

@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Dec 10, 2019

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

@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Dec 10, 2019

azure-sdk-for-net - 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

@jhendrixMSFT jhendrixMSFT merged commit 1b0a93c into Azure:master Dec 10, 2019
@brjohnstmsft brjohnstmsft deleted the search-rename-cog-services branch December 10, 2019 00:31
TalluriAnusha pushed a commit to AsrOneSdk/azure-rest-api-specs that referenced this pull request Dec 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants