[Backup] increasing VM protection limit from 100 to 1000 #15563
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
|
cc @houk-ms for error message |
Member
Author
|
/azp run |
|
Commenter does not have sufficient privileges for PR 15563 in repo Azure/azure-cli |
Member
Author
|
@fengzhou-msft please trigger a rerun for the azure pipeline build checks. I do not have sufficient permissions to do so |
Member
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
fengzhou-msft
approved these changes
Oct 20, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Relaxed the client side limit for AzureIaasVM protection from 100 to 1000
Testing Guide
History Notes
[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.
This checklist is used to make sure that common guidelines for a pull request are followed.
[Yes ] The PR title and description has followed the guideline in Submitting Pull Requests.
[Yes ] I adhere to the Command Guidelines.