Introduce API version 2020-06-01#10117
Introduce API version 2020-06-01#10117weidongxu-microsoft merged 9 commits intoAzure:masterfrom naveedaz:master
Conversation
[Staging] Swagger Validation Report
️✔️ |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Can one of the admins verify this patch? |
azure-sdk-for-python - Release
|
azure-sdk-for-net - 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-java - Release
|
azure-sdk-for-js - 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-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-go - Release
|
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Please review Linter errors and warnings. Specific errors below.
|
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@chiragg4u The issue below is not a new issue. It existed in previous API version too. The property is not owned by the App service control plane but the functions runtime. The API surface just fwds the request. |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Please review all linter errors and warnings. |
|
There is still simple Avodado and PrettierCheck failures. |
|
@mathewc The ask here is to change the property name from trigger_url to triggerUrl in the /admin/host/synctriggers fx runtime API. Please add a tracking item for future work. @weidongxu-microsoft I will add a suppression to unblock for now. |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@weidongxu-microsoft @chiragg4u Please review and merge. |
|
@chiragg4u |
|
While adding new version the recommendation is to copy the existing version into new directory structure for first commit and then push new changes for easy review. |
|
Looks like you've just copied the files into new version in this case no formal review required. In case there are changes where you require ARM API review please update the PR with the above recommendation for easy review, |
* Introduce API version 2020-06-01 * Add custom word FDID. Reference: https://azure.microsoft.com/en-us/updates/azure-front-door-march-2020-updates/ * Add clientCertMode and customDomainVerificationId * Adding some missing models * Some more missing models * Remove APIs with issues * Fix spacing issue in web app * Fix per code review recommendations * Fix prettier issue and change path in suppression Co-authored-by: Naveed Aziz <naveeda@ntdev.microsoft.com>
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.