-
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
Azure Backup Version 2019-05-13 addition #7345
Conversation
New api version 2019-05-13 for ProtectedItems_Get,ProtectedItems_CreateOrUpdate,RecoveryPoints_List,RecoveryPoints_Get,Restores_Trigger, BackupJobs_List, BackupProtectedItems_List and version 2017-07-01 for ProtectionPolicies_CreateOrUpdate
In Testing, Please Ignore[Logs] (Generated from 94fc988, Iteration 31).NET: test-repo-billy/azure-sdk-for-net [Logs] [Diff]
Python: test-repo-billy/azure-sdk-for-python [Logs] [Diff]
Java: test-repo-billy/azure-sdk-for-java [Logs] [Diff]
Go: test-repo-billy/azure-sdk-for-go [Logs] [Diff]
JavaScript: test-repo-billy/azure-sdk-for-js [Logs] [Diff]
Ruby: test-repo-billy/azure-sdk-for-ruby [Logs] [Diff]
|
Automation for azure-sdk-for-goThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-pythonThe initial PR has been merged into your service PR: |
Can one of the admins verify this patch? |
@SanjayHukumRana , could you take a look at those errors from the checks? |
Fixing inconsistent description for recoverytype across workloads
Hi @renhe Li<mailto:[email protected]>,
I have updated the PR multiple times but unable to understand this failure.
Can you please thrown some light on this like where it this picking incompatible values and how to fix it?
($.paths[\\"/Subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupstorageconfig/vaultstorageconfig\\"].patch.operationId)"\n}\nProcess() cancelled due to exception : \'$.definitions.AzureFileShareRestoreRequest.properties.recoveryType.enum\' has incompatible values (---\n- Invalid\n- OriginalLocation\n- AlternateLocation\n- RestoreDisks\n- Offline\n, ---\n- Invalid\n- OriginalLocation\n- AlternateLocation\n- RestoreDisks\n).\n{\n "Channel": "fatal",\n "Text": "swagger-document/compose - FAILED"\n},\n{\n "Channel": "fatal",\n "Text": "Error: \'$.definitions.AzureFileShareRestoreRequest.properties.recoveryType.enum\' has incompatible values (---\\n- Invalid\\n- OriginalLocation\\n- AlternateLocation\\n- RestoreDisks\\n- Offline\\n, ---\\n- Invalid\\n- OriginalLocation\\n- AlternateLocation\\n- RestoreDisks\\n)."\n}\n(node:5399) UnhandledPromiseRejectionWarning: Error: \'$.definitions.AzureFileShareRestoreRequest.properties.recoveryType.enum\' has incompatible values (---\n- Invalid\n- OriginalLocation\n- AlternateLocation\n- RestoreDisks\n- Offline\n, ---\n- Invalid\n- OriginalLocation\n- AlternateLocation\n- RestoreDisks\n).\n at Merge (/home/vsts/.autorest/@[email protected]/node_modules/@microsoft.azure/autorest-core/dist/lib/source-map/merging.js:58:11)\n at Merge (/home/vsts/.autorest/@microsoft.azure_autorest-co
Thanks.
From: Renhe Li <[email protected]>
Sent: 29 September 2019 08:53
To: Azure/azure-rest-api-specs <[email protected]>
Cc: Sanjay Rana <[email protected]>; Mention <[email protected]>
Subject: Re: [Azure/azure-rest-api-specs] Azure Backup Version 2019-05-13 addition (#7345)
@SanjayHukumRana<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSanjayHukumRana&data=02%7C01%7Crsanjay%40microsoft.com%7C7ff98e74b2be41dbae7e08d7448c64a3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637053242082404010&sdata=4ORhi3kzwNajOPVXezNtW2HcE9htYSAGZw1oTR9L4wg%3D&reserved=0> , could you take a look at those errors from the checks?
—
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%2F7345%3Femail_source%3Dnotifications%26email_token%3DALCW2DB4OYQKUN7QZLAORCLQMANS5A5CNFSM4I3F7ZJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD73HDVY%23issuecomment-536244695&data=02%7C01%7Crsanjay%40microsoft.com%7C7ff98e74b2be41dbae7e08d7448c64a3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637053242082404010&sdata=zfOD3YXEeL1jbDRcoWSCaBcnunnE4G5jHw7e8SK8cDs%3D&reserved=0>, or mute the thread<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FALCW2DFTN5NTWWYDN64HSZ3QMANS5ANCNFSM4I3F7ZJA&data=02%7C01%7Crsanjay%40microsoft.com%7C7ff98e74b2be41dbae7e08d7448c64a3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637053242082413997&sdata=yoNwubBqoVKyGQj6ofwa%2F39qZXNz5qwjUo0kpSKOlA8%3D&reserved=0>.
|
Hi Renhe Li, I have updated the PR multiple times but unable to understand this failure in lintdiff. ( Thanks. |
Can we have tool to run this privately over the changes or can we have all the breaking changes in single go rather than one by one?
Getting them one by one and fixing them one by one
I added ARMReviewMeetingRequired to track the conversation with John Gossman and Mark Simms. Once direction is resolved with them, I'll review the changes as the PR could change drastically. |
John Gossman approved the full deprecation of the api version. |
...ecoveryservicesbackup/resource-manager/Microsoft.RecoveryServices/stable/2016-12-01/bms.json
Outdated
Show resolved
Hide resolved
...t.RecoveryServices/stable/2016-12-01/examples/AzureIaasVm/ProtectedItemOperationResults.json
Show resolved
Hide resolved
...-manager/Microsoft.RecoveryServices/stable/2017-07-01/examples/Common/TriggerExportJobs.json
Show resolved
Hide resolved
...ecoveryservicesbackup/resource-manager/Microsoft.RecoveryServices/stable/2019-05-13/bms.json
Show resolved
Hide resolved
...ecoveryservicesbackup/resource-manager/Microsoft.RecoveryServices/stable/2019-05-13/bms.json
Show resolved
Hide resolved
...ecoveryservicesbackup/resource-manager/Microsoft.RecoveryServices/stable/2019-05-13/bms.json
Show resolved
Hide resolved
...ecoveryservicesbackup/resource-manager/Microsoft.RecoveryServices/stable/2019-05-13/bms.json
Outdated
Show resolved
Hide resolved
...ecoveryservicesbackup/resource-manager/Microsoft.RecoveryServices/stable/2019-05-13/bms.json
Outdated
Show resolved
Hide resolved
...ecoveryservicesbackup/resource-manager/Microsoft.RecoveryServices/stable/2019-05-13/bms.json
Show resolved
Hide resolved
...ecoveryservicesbackup/resource-manager/Microsoft.RecoveryServices/stable/2019-05-13/bms.json
Outdated
Show resolved
Hide resolved
Moving Patch and Get of vault config to 2019-05-13
Policy comment is still pending
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.
Looks like there is one last change that was missed.
...ecoveryservicesbackup/resource-manager/Microsoft.RecoveryServices/stable/2016-12-01/bms.json
Show resolved
Hide resolved
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.
Approved from ARMs side
New api version 2019-05-13 for ProtectedItems_Get,ProtectedItems_CreateOrUpdate,RecoveryPoints_List,RecoveryPoints_Get,Restores_Trigger, BackupJobs_List, BackupProtectedItems_List and version 2017-07-01 for ProtectionPolicies_CreateOrUpdate
Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Contribution checklist:
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.