-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Add 2020-02-02-preview related to new ImportExport API #10428
Conversation
You don't have permission to trigger SDK Automation. |
[Staging] Swagger Validation Report
️✔️ |
Can one of the admins verify this patch? |
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.
Approving with a cautionary note about the change in /import URI from the old api-version
Hey Chris,
I have discussed with my team, and we are ok if we have one-time cost to change permissions for users upgrading to new API. The old API version should still be available for a while for users who don’t want to do this right away.
Can you please merge the PR?
Thanks,
Brandon
From: Chris Eggert <notifications@github.com>
Sent: Wednesday, August 26, 2020 1:39 PM
To: Azure/azure-rest-api-specs <azure-rest-api-specs@noreply.github.com>
Cc: Brandon Greenwood <brandong@microsoft.com>; Mention <mention@noreply.github.com>
Subject: Re: [Azure/azure-rest-api-specs] Add 2020-02-02-preview related to new ImportExport API (#10428)
@pilor approved this pull request.
Approving with a cautionary note about the change in /import URI from the old api-version
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-rest-api-specs%2Fpull%2F10428%23pullrequestreview-475841348&data=02%7C01%7Cbrandong%40microsoft.com%7C58a64971abef4dd6c4f408d84a00137b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637340711473213830&sdata=ho%2FSyuaw4mOkX1AT4zM8NfYuwpGghegw4Queb2q7yo0%3D&reserved=0>, or unsubscribe<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAKUNCGQN23S2YEBY6FF6HFDSCVXGTANCNFSM4P3WYVJQ&data=02%7C01%7Cbrandong%40microsoft.com%7C58a64971abef4dd6c4f408d84a00137b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637340711473223829&sdata=ZZRTB4VQjngIr5tvJD6e6D6BLMnB41zrJAPHFXOeFnY%3D&reserved=0>.
|
The SDK reviewer (@erich-wang) needs to review and merge. API reviewers don't merge |
/azp run |
Azure Pipelines successfully started running 3 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-java - Release
|
azure-sdk-for-net - Release
|
azure-sdk-for-go - 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
|
azure-sdk-for-python
- Breaking Change detected in SDK
|
azure-resource-manager-schemas - Release
|
azure-sdk-for-js - Release
|
I was told that we could ignore |
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
|
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
Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.
If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.
Please follow the link to find more details on PR review process.