-
Notifications
You must be signed in to change notification settings - Fork 5.6k
Update CDN default api version to 2020-04-15. #10026
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
Conversation
[Staging] Swagger Validation Report
️✔️ |
|
Azure Pipelines successfully started running 1 pipeline(s). |
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-go - Release
|
azure-sdk-for-java - Release
|
azure-sdk-for-js - Release
|
azure-sdk-for-net - Release
|
azure-sdk-for-python - Release
- Breaking Change detected in SDK
|
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
|
|
Can one of the admins verify this patch? |
|
Let me know if the lint error can be fixed. Or it would need code owner's help. |
|
@weidongxu-microsoft, these linter errors are existing issues that are getting flagged as new because of the change in API version, and fixing them is beyond the scope of this PR. Can we merge this PR and plan to fix those issues in a future PR? |
@akning-ms Hello Arthur, are you OK to merge it? No change in spec, all lint issue is existing ones. |
|
Hi @lsmith130, Can I know why you change this default tag to new version? it is for release SDK? if yes. suggest you to fix the lint error first. otherwise, it will cause more impact for customer if change after sdk release. as fix the linter error may change breaking change |
|
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
|
|
@akning-ms, I've fixed the warnings that can be done reasonably, and the errors are saying that the error response format doesn't match the standard, which is incorrect. Our error format does match the standard, and changes to the error format would be a breaking change for all existing resource types. The only remaining warnings that cannot be fixed later are the warnings that enums should be used as booleans, but because these warnings were not enforced before merging the original PR that introduced them, we've already done substantial engineering effort on the assumption that the boolean fields are acceptable. Can we move forward with this PR or do I need to convince my team to make updates to multiple accepted API versions and redo work in our RP that is already tested and working? |
|
Thanks for clarify, @lsmith130 make sense, LGTM if you have plan to fix it. |
* Update CDN default api version to 2020-04-15 * Add missing CDN x-ms-enum fields for url signing.
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.