-
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
Fixing migrate swagger issues #9949
Conversation
You don't have permission to trigger SDK Automation. |
[Staging] Swagger Validation Report
❌ |
Can one of the admins verify this patch? |
Fixing prettier.
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
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
|
azure-sdk-for-go - Release
|
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
|
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-js - 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-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
|
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
|
Fixing some more things.
@@ -2209,9 +2202,6 @@ | |||
} | |||
} | |||
}, | |||
"x-ms-pageable": { |
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 API is pageable. ARM will return a nextLink if one of your regional endpoints doesn't respond in time or has a retryable error.
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.
applies to any collection GETs on tracked reosurces
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.
nextLinkName should be specified (and equal "nextLink") and the response in the subscription and resource group level collection GETs should return a nextLink property (the definition does not contain it right now). Your RP doesn't control whether ARM returns a nextLink here or not and the SDK should be set up to follow it if it is returned.
@@ -2580,9 +2546,6 @@ | |||
} | |||
} | |||
}, | |||
"x-ms-pageable": { |
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 are you removing x-ms-pageable from your proxy resource collection GETs? You can keep this even if you never return a nextLink value. If your definition doesn't have a "nextLink" property "nextLinkName" can be null. https://github.com/Azure/autorest/blob/master/docs/extensions/readme.md#x-ms-pageable
Taking commenst.
@@ -2209,9 +2202,6 @@ | |||
} | |||
} | |||
}, | |||
"x-ms-pageable": { |
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.
nextLinkName should be specified (and equal "nextLink") and the response in the subscription and resource group level collection GETs should return a nextLink property (the definition does not contain it right now). Your RP doesn't control whether ARM returns a nextLink here or not and the SDK should be set up to follow it if it is returned.
Taking comments
/azp run automation - sdk |
Azure Pipelines successfully started running 1 pipeline(s). |
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.