-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
[Public-Preview] Review request for Microsoft.Migrate to add version … #9883
Conversation
…preview/2019-10-01-preview
[Staging] Swagger Validation Report
️✔️ |
Azure Pipelines successfully started running 1 pipeline(s). |
Can one of the admins verify this patch? |
azure-sdk-for-go - Release
|
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-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
|
azure-sdk-for-python - Release
|
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-java - Release
|
Azure Pipelines successfully started running 1 pipeline(s). |
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
|
b3a19c9
to
5a6db0b
Compare
Azure Pipelines successfully started running 1 pipeline(s). |
5a6db0b
to
2b75111
Compare
Azure Pipelines successfully started running 1 pipeline(s). |
2b75111
to
060c79b
Compare
Azure Pipelines successfully started running 1 pipeline(s). |
060c79b
to
5633341
Compare
Azure Pipelines successfully started running 1 pipeline(s). |
...move/resource-manager/Microsoft.Migrate/preview/2019-10-01-preview/regionmovecollection.json
Show resolved
Hide resolved
}, | ||
"MoveState": { | ||
"description": "Defines the MoveResource states.", | ||
"enum": [ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will you consider using x-ms-enum (https://github.com/Azure/autorest/tree/master/docs/extensions#x-ms-enum) for better code generation?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, i have added this. This is an additional information on the enum and as I have understood does not require any change from service.
@@ -0,0 +1,79 @@ | |||
# regionmove |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why do you use a separate location for the readme files?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey, when we raised this PR earlier for private preview, these files were auto-generated by HUB.
However, what is the location preferred for readme files?
...move/resource-manager/Microsoft.Migrate/preview/2019-10-01-preview/regionmovecollection.json
Outdated
Show resolved
Hide resolved
...move/resource-manager/Microsoft.Migrate/preview/2019-10-01-preview/regionmovecollection.json
Show resolved
Hide resolved
...move/resource-manager/Microsoft.Migrate/preview/2019-10-01-preview/regionmovecollection.json
Show resolved
Hide resolved
...move/resource-manager/Microsoft.Migrate/preview/2019-10-01-preview/regionmovecollection.json
Show resolved
Hide resolved
...move/resource-manager/Microsoft.Migrate/preview/2019-10-01-preview/regionmovecollection.json
Show resolved
Hide resolved
Azure Pipelines successfully started running 1 pipeline(s). |
5c37328
to
cb04c75
Compare
Azure Pipelines successfully started running 1 pipeline(s). |
} | ||
], | ||
"responses": { | ||
"200": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this operation is marked as long running but does not have a long running response code
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
removed it as the operation is not long running, thanks.
} | ||
], | ||
"responses": { | ||
"200": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
patch async requires 202
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
removed the long running from PUT/PATCH of move collection.
} | ||
}, | ||
"x-ms-pageable": { | ||
"nextLinkName": null |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you don't control whether there is a nextLink on subscription and RG Level GETs for tracked resources. It must be supported because ARM may return it for you if one of your regional endpoints does not return a response in time or returns a retryable error code
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Got it, i have added the "nextLink" in both RG level and subscription level GETs.
cb04c75
to
d20f294
Compare
Azure Pipelines successfully started running 1 pipeline(s). |
Private-preview PR request: https://github.com/Azure/azure-rest-api-specs-pr/pull/968
Status: ARMSignedOff
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
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.