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

[AKS]: Remove 200/OK response from reset SP/AAD api #4948

Merged
merged 10 commits into from
Jan 8, 2019

Conversation

zqingqing1
Copy link
Member

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.

@openapi-portal-comment
Copy link

If you're a MSFT employee, click this link
to view this PR's validation status on our new OpenAPI Hub spec management tool.

@AutorestCI
Copy link

AutorestCI commented Dec 19, 2018

Automation for azure-sdk-for-js

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-js#816

@AutorestCI
Copy link

AutorestCI commented Dec 19, 2018

Automation for azure-sdk-for-ruby

Nothing to generate for azure-sdk-for-ruby

@AutorestCI
Copy link

AutorestCI commented Dec 19, 2018

Automation for azure-sdk-for-python

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-python#4064

@AutorestCI
Copy link

AutorestCI commented Dec 19, 2018

Automation for azure-sdk-for-java

Nothing to generate for azure-sdk-for-java

@AutorestCI
Copy link

AutorestCI commented Dec 19, 2018

Automation for azure-sdk-for-node

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-node#4437

@AutorestCI
Copy link

AutorestCI commented Dec 19, 2018

Automation for azure-sdk-for-go

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-go#3831

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

Copy link
Member

@jhendrixMSFT jhendrixMSFT left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need confirmation from @ravbhatnagar that returning 202 from a synchronous operation is ok.

@azuresdkci
Copy link
Contributor

Hello!!

The Rest API Specs team wishes everyone a happy holiday and would like to kindly inform you that responses and review to Pull request will be delayed during the holiday period (now -> 2nds of January) to allow for Awesome reviewers to have an awesome time with their families during the holidays!

Thanks and Have a WONDERFUL HOLIDAY

@jhendrixMSFT
Copy link
Member

@zqingqing1 can you please explain why this is being removed? It's introducing new SDK validation failures, see here. Current requirement is to model the terminal LRO state in the swagger.

@zqingqing1
Copy link
Member Author

The reason why it is been removed, because 200 is not in the response status of these 2 APIs. So right now, I am thinking maybe we can return operation status as 200 after polling header, if we wanna resolve this error.

@jhendrixMSFT
Copy link
Member

@lmazuel I was told you asked to have this validation rule put in place. Can you please explain the details behind it?

@zqingqing1
Copy link
Member Author

@jhendrixMSFT, I added 200 response to resolve the error. Please review :)

@jhendrixMSFT
Copy link
Member

@zqingqing1 there is a merge conflict, can you please resolve it?

@zqingqing1
Copy link
Member Author

@jhendrixMSFT have time to review again?

@jhendrixMSFT
Copy link
Member

@AutorestCI regenerate azure-sdk-for-go

@jhendrixMSFT
Copy link
Member

With these changes the generated code no longer returns a ManagedCluster object when the LRO completes. Take a look at the Go codegen for an example. Is this expected?

@zqingqing1
Copy link
Member Author

Yes, it is expected.

@jhendrixMSFT
Copy link
Member

So when the polling completes the user needs to make a separate API call then to retrieve the result?

@zqingqing1
Copy link
Member Author

Yes, that is right.

@jhendrixMSFT jhendrixMSFT merged commit fe884fb into Azure:master Jan 8, 2019
TalluriAnusha pushed a commit to AsrOneSdk/azure-rest-api-specs that referenced this pull request Feb 6, 2019
* add  operation for 2018-03-31 and 2018-08-01-preview

* correct example fileName

* add default response and 202, correct typo

* remove 200 response

* long running operation

* return 202 with no body

* forget to remove 202 body from 2018-08-01-preview api

* add 200 without schema
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.

5 participants