Add new ANF API 2019-11-01#8164
Conversation
ANF-567 add API 2019-11-01
ANF-567 add API 2019-11-01
|
Azure Pipelines successfully started running 1 pipeline(s). |
Prettier
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@iscai-msft you were a suggested reviewer but I also have a question. I'm wondering why the pipeline shows some checks were not successful even though no steps actually show as failed. Do you know why this is? One does show as cancelled. Do you know why this one is cancelled? |
ANF-567 add API 2019-11-01
|
Azure Pipelines successfully started running 1 pipeline(s). |
1 similar comment
|
Azure Pipelines successfully started running 1 pipeline(s). |
azure-sdk-for-go - Release
|
azure-sdk-for-java - Release
|
azure-sdk-for-net - Release
|
azure-sdk-for-python - Release
|
azure-sdk-for-js - Release
|
ANF-567 add API 2019-11-01
|
Azure Pipelines successfully started running 1 pipeline(s). |
| } | ||
| }, | ||
| "/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.NetApp/netAppAccounts/{accountName}/capacityPools/{poolName}/volumes/{volumeName}/revert": { | ||
| "post": { |
There was a problem hiding this comment.
post [](start = 7, length = 4)
you are missing the x-ms-long-running-operation annotation - please take a look at https://github.com/Azure/autorest/blob/master/docs/extensions/readme.md#x-ms-long-running-operation
There was a problem hiding this comment.
Yes. This was also pointed out in the review for the previous swagger which was accepted. We created an open internal ticket on this issue to investigate.
The fact is that adding this results in a failure from the autorest validation 'ERROR (LongRunningResponseStatusCode/R2005/SDKViolation): A 'POST' operation 'Volumes_Revert' with x-ms-long-running-operation extension must have a valid terminal success status code 200 or 201 or 204.'
But perhaps you have some idea how to solve this?
There was a problem hiding this comment.
Yup. Due to limitations of the current version of OpenAPiSpec (aka Swagger), we don't have a good way of modeling the final response on a long running operation (the response on the GET on the async operation URL).
The, somewhat counterintuitive, workaround is to add a 200 response to this path. By convention the code generator will understand that your service is not returning the 200 response for this POST, but that this is the final operation result instead. Does that make sense?
In reply to: 369432464 [](ancestors = 369432464)
There was a problem hiding this comment.
So I just need to add a (dummy) 200 response block. I'll update.
There was a problem hiding this comment.
@majastrz Update made. But I notice some validation checks did not run.
majastrz
left a comment
There was a problem hiding this comment.
Please take a look at the comment I added.
Correct long running operations - add dummy terminal 200 state
ANF-567 add new API 2019-11-01
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@NullMDR any idea why some of the checks got cancelled? How do we restart them? |
|
/azp run automation - sdk |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Any chance this could be merged? I see there is a failure however but it seems to be a problem of the job not the swagger "Failed to run SDK Automation: Error: SDK Automation failed" |
* ANF-567 add API 2019-11-01 * ANF-567 add API 2019-11-01 * Update netapp.json Prettier * ANF-567 add API 2019-11-01 * ANF-567 add API 2019-11-01 * ANF-567 add new API 2019-11-01 Correct long running operations - add dummy terminal 200 state
* ANF-567 add API 2019-11-01 * ANF-567 add API 2019-11-01 * Update netapp.json Prettier * ANF-567 add API 2019-11-01 * ANF-567 add API 2019-11-01 * ANF-567 add new API 2019-11-01 Correct long running operations - add dummy terminal 200 state
Removal of mount target list operation and change to response properties.
Addition of site property.
Removal of snapshot tags property.
Add missing revert volume to snapshot.
Amend property in authorize example.
Other minor amendments.
(Internal ticket ANF-567)
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.