Add breaking change warning message for Start-AzStorageAccountMigration cmdlet #27396
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
| Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
EmmaZhu
force-pushed
the
storage/migration_break_warning
branch
from
fcd9561 to
25f2acf
Compare
Member
|
/azp run |
notyashhh
added
the
Breaking Change Preannounce
Contributor
|
Azure Pipelines successfully started running 3 pipeline(s). |
Collaborator
|
VeryEarly
reviewed
Mar 21, 2025
| internal | ||
| exports | ||
| tools | ||
| custom/*.psm1 |
Collaborator
There was a problem hiding this comment.
- please run autorest --reset to get latest autorest
- re-run autorest to regenerate
- make sure update in this file was checked in
EmmaZhu
force-pushed
the
storage/migration_break_warning
branch
2 times, most recently
from
016c37b to
69940b6
Compare
blueww
reviewed
Mar 24, 2025
| Set-AzStorageAccountManagementPolicy [-ResourceGroupName] <String> [-StorageAccountName] <String> | ||
| -Rule <PSManagementPolicyRule[]> [-DefaultProfile <IAzureContextContainer>] [-WhatIf] [-Confirm] | ||
| [<CommonParameters>] | ||
| -Rule <PSManagementPolicyRule[]> [-DefaultProfile <IAzureContextContainer>] |
Member
There was a problem hiding this comment.
Please revert change of this file. the file don't need change.
@VeryEarly It looks the file will have several repeated parameters when run build-module again. It would be great if you could help to resolve it!
Collaborator
|
/azp run |
Contributor
|
Azure Pipelines successfully started running 3 pipeline(s). |
EmmaZhu
force-pushed
the
storage/migration_break_warning
branch
from
69940b6 to
ac0148b
Compare
Collaborator
|
/azp run |
Contributor
|
Azure Pipelines successfully started running 3 pipeline(s). |
blueww
approved these changes
Mar 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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
The warning message will be shown like:
Mandatory Checklist
Please choose the target release of Azure PowerShell. (⚠️ Target release is a different concept from API readiness. Please click below links for details.)
Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.mdand reviewed the following information:ChangeLog.mdfile(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.## Upcoming Releaseheader in the past tense.ChangeLog.mdif no new release is required, such as fixing test case only.