generate migration guide for Az 12.0.0 #24877
Merged
Conversation
This file contains 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
️✔️Az.Accounts
|
Co-authored-by: Yeming Liu <11371776+isra-fel@users.noreply.github.com>
|
|
||
| #### Before | ||
| ```powershell | ||
| New-AzGalleryImageDefinition -ResourceGroupName $rgName -GalleryName $galleryName -Name $galleryImageDefinitionName -Location $location -Publisher $publisherName -Offer $offerName -Sku $skuName -OsState "Specialized" -OsType "Linux" defaulted to HyperVGeneration Gen1 and SecurityType Standard in the service side |
There was a problem hiding this comment.
I put some unnecesarry space after "Linux" in the excel sheet here, but maybe we remove it here?
There was a problem hiding this comment.
It's removed. Please check it.
| ``` | ||
| #### After | ||
| ```powershell | ||
| Will default to HyperVGeneration Gen2 and SecurityType TrustedLaunchSupported by code in service side |
There was a problem hiding this comment.
Same cmdlet let above will default to -
There was a problem hiding this comment.
updated. Please check it.
blueww
previously approved these changes
May 11, 2024
There was a problem hiding this comment.
The migration guild of set-azstorageaccount and Set-AzStorageFileContent looks good to me.
@yifanz7 Would you please check the Queue related items: https://github.com/Azure/azure-powershell/blob/bed87a12d5c4e2c38bd4cded217e5b7af0be49a3/documentation/migration-guides/Az.12.0.0.0-migration-guide.md#azstorage
Sandido
requested changes
May 13, 2024
YanaXu
force-pushed
the
yanxu/migrationguide
branch
from
d3448ae
to
3521224
Compare
yifanz7
reviewed
May 13, 2024
Co-authored-by: yifanz7 <131133995+yifanz7@users.noreply.github.com>
Sandido
requested changes
May 13, 2024
| ``` | ||
| #### After | ||
| ```powershell | ||
| $vm = New-AzVM -ResourceGroupName $rgname -Name $vmname -Credential $cred -SecurityType $securityTypeST -DomainNameLabel $domainNameLabel |
There was a problem hiding this comment.
Suggested change
| $vm = New-AzVM -ResourceGroupName $rgname -Name $vmname -Credential $cred -SecurityType $securityTypeST -DomainNameLabel $domainNameLabel | |
| $vm = New-AzVM -ResourceGroupName $rgname -Name $vmname -Credential $cred -SecurityType "Standard" -DomainNameLabel $domainNameLabel |
| ### `New-AzGalleryImageDefinition` | ||
|
|
||
| - Cmdlet breaking-change will happen to all parameter sets | ||
| - Starting in May 2024 the "New-AzGalleryImage" cmdlet will deploy with the Trusted Launch configuration by default. To know more about Trusted Launch, please visit https://docs.microsoft.com/en-us/azure/virtual-machines/trusted-launch |
There was a problem hiding this comment.
Suggested change
| - Starting in May 2024 the "New-AzGalleryImage" cmdlet will deploy with the Trusted Launch configuration by default. To know more about Trusted Launch, please visit https://docs.microsoft.com/en-us/azure/virtual-machines/trusted-launch | |
| - Starting in May 2024 the "New-AzGalleryImage" cmdlet will deploy with the Trusted Launch configuration and Gen2 Hyper V Generation by default. To know more about Trusted Launch, please visit https://docs.microsoft.com/en-us/azure/virtual-machines/trusted-launch |
There was a problem hiding this comment.
Suggested change
| - Starting in May 2024 the "New-AzGalleryImage" cmdlet will deploy with the Trusted Launch configuration by default. To know more about Trusted Launch, please visit https://docs.microsoft.com/en-us/azure/virtual-machines/trusted-launch | |
| - Starting in May 2024 the "New-AzGalleryImage" cmdlet will deploy with the Trusted Launch configuration and Gen2 Hyper V Generation by default. To know more about Trusted Launch, please visit [https://learn.microsoft.com/azure/virtual-machines/trusted-launch](/azure/virtual-machines/trusted-launch) |
There was a problem hiding this comment.
This URL causes a hard-coded-locale and docs-link-absolute build warning in the docs repo.
| #### Before | ||
| ```powershell | ||
| Get-AzVmss -ResourceGroupName "" | ||
| # returned empty list |
There was a problem hiding this comment.
Suggested change
| # returned empty list | |
| # Returned an empty list. |
| #### After | ||
| ```powershell | ||
| Get-AzVmss -ResourceGroupName "" | ||
| # will return error for empty string validation in the parameter |
There was a problem hiding this comment.
Suggested change
| # will return error for empty string validation in the parameter | |
| # Will return an error from empty string validation in the parameter. |
| #### Before | ||
| ```powershell | ||
| New-AzGalleryImageDefinition -ResourceGroupName $rgName -GalleryName $galleryName -Name $galleryImageDefinitionName -Location $location -Publisher $publisherName -Offer $offerName -Sku $skuName -OsState "Specialized" -OsType "Linux" | ||
| # defaulted to HyperVGeneration Gen1 and SecurityType Standard in the service side |
There was a problem hiding this comment.
Suggested change
| # defaulted to HyperVGeneration Gen1 and SecurityType Standard in the service side | |
| # Defaulted to HyperVGeneration: Gen1 and SecurityType: Standard in the service side . |
| ``` | ||
| #### After | ||
| ```powershell | ||
| # Will default to HyperVGeneration Gen2 and SecurityType TrustedLaunchSupported by code in service side |
There was a problem hiding this comment.
Suggested change
| # Will default to HyperVGeneration Gen2 and SecurityType TrustedLaunchSupported by code in service side | |
| New-AzGalleryImageDefinition -ResourceGroupName $rgName -GalleryName $galleryName -Name $galleryImageDefinitionName -Location $location -Publisher $publisherName -Offer $offerName -Sku $skuName -OsState "Specialized" -OsType "Linux" | |
| # Defaults to HyperVGeneration: Gen2 and SecurityType: TrustedLaunchSupported at the PowerShell level. |
mikefrobbins
requested changes
May 14, 2024
| ### `New-AzVM` | ||
|
|
||
| - Cmdlet breaking-change will happen to all parameter sets | ||
| - Starting in May 2024 the "New-AzVM" cmdlet will deploy with the image 'Windows Server 2022 Azure Edition' by default. This will make migrating to Trusted Launch easier in the future. To know more about Trusted Launch, please visit https://docs.microsoft.com/en-us/azure/virtual-machines/trusted-launch |
There was a problem hiding this comment.
Suggested change
| - Starting in May 2024 the "New-AzVM" cmdlet will deploy with the image 'Windows Server 2022 Azure Edition' by default. This will make migrating to Trusted Launch easier in the future. To know more about Trusted Launch, please visit https://docs.microsoft.com/en-us/azure/virtual-machines/trusted-launch | |
| - Starting in May 2024 the "New-AzVM" cmdlet will deploy with the image 'Windows Server 2022 Azure Edition' by default. This will make migrating to Trusted Launch easier in the future. To know more about Trusted Launch, please visit [https://learn.microsoft.com/azure/virtual-machines/trusted-launch](/azure/virtual-machines/trusted-launch) |
There was a problem hiding this comment.
This link causes a hard-coded-locale and docs-link-absolute build warning in the docs repo.
| ### `New-AzVmss` | ||
|
|
||
| - Cmdlet breaking-change will happen to all parameter sets | ||
| - Starting in May 2024 the "New-AzVmss" cmdlet will deploy with the image 'Windows Server 2022 Azure Edition' by default. This will make migrating to Trusted Launch easier in the future. To know more about Trusted Launch, please visit https://docs.microsoft.com/en-us/azure/virtual-machines/trusted-launch |
There was a problem hiding this comment.
Suggested change
| - Starting in May 2024 the "New-AzVmss" cmdlet will deploy with the image 'Windows Server 2022 Azure Edition' by default. This will make migrating to Trusted Launch easier in the future. To know more about Trusted Launch, please visit https://docs.microsoft.com/en-us/azure/virtual-machines/trusted-launch | |
| - Starting in May 2024 the "New-AzVmss" cmdlet will deploy with the image 'Windows Server 2022 Azure Edition' by default. This will make migrating to Trusted Launch easier in the future. To know more about Trusted Launch, please visit [https://learn.microsoft.com/azure/virtual-machines/trusted-launch](/azure/virtual-machines/trusted-launch) |
| ### `New-AzEventGridPartnerRegistration` | ||
|
|
||
| - Cmdlet breaking-change will happen to all parameter sets | ||
| - Added new required parameter: Location <String> |
There was a problem hiding this comment.
Suggested change
| - Added new required parameter: Location <String> | |
| - Added new required parameter: Location `<String>` |
There was a problem hiding this comment.
This line causes a disallowed-html-tag docs build warning.
| ### `New-AzGalleryImageDefinition` | ||
|
|
||
| - Cmdlet breaking-change will happen to all parameter sets | ||
| - Starting in May 2024 the "New-AzGalleryImage" cmdlet will deploy with the Trusted Launch configuration by default. To know more about Trusted Launch, please visit https://docs.microsoft.com/en-us/azure/virtual-machines/trusted-launch |
There was a problem hiding this comment.
Suggested change
| - Starting in May 2024 the "New-AzGalleryImage" cmdlet will deploy with the Trusted Launch configuration by default. To know more about Trusted Launch, please visit https://docs.microsoft.com/en-us/azure/virtual-machines/trusted-launch | |
| - Starting in May 2024 the "New-AzGalleryImage" cmdlet will deploy with the Trusted Launch configuration and Gen2 Hyper V Generation by default. To know more about Trusted Launch, please visit [https://learn.microsoft.com/azure/virtual-machines/trusted-launch](/azure/virtual-machines/trusted-launch) |
| ### `New-AzGalleryImageDefinition` | ||
|
|
||
| - Cmdlet breaking-change will happen to all parameter sets | ||
| - Starting in May 2024 the "New-AzGalleryImage" cmdlet will deploy with the Trusted Launch configuration by default. To know more about Trusted Launch, please visit https://docs.microsoft.com/en-us/azure/virtual-machines/trusted-launch |
There was a problem hiding this comment.
This URL causes a hard-coded-locale and docs-link-absolute build warning in the docs repo.
…-powershell into yanxu/migrationguide
|
Hi @mikefrobbins & @grizzlytheodore , I've updated the md file based on your comments. Please check it. Thanks. |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
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.