May breaking change warnings for New-AzVM, New-AzVmss, New-AzGalleryImage #24437
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
https://msazure.visualstudio.com/One/_workitems/edit/27249508
We received 3 requests for a breaking change in the May release recently, so we want to put in these warnings.
New-AzVM and New-AzVmss will use a new default image (instead of Win2016Datacenter, it will use Win2022AzureEdition) if the user provides none and if the user specifies the securityType of Standard.
These cmdlets have very high usage per week.
New-AzGalleryImageDefinition. The feature TrustedLaunchSupported will now be turned on by default and HyperVGeneration will be set to V2 unless the user specifies otherwise.
Get-AzVmss returns nothing when an empty resource group and/or vm scale set name are passed in as empty. The change is to throw an error here. In other cmdlets, like Get-AzVM, the expected pattern is that the cmdlet will error out when not provided with these pieces.
I guessed that the May Breaking Change release will have the compute version 8.0.0.
Mandatory Checklist
Please choose the target release of Azure PowerShell
Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.md
and reviewed the following information:ChangeLog.md
file(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
.## Upcoming Release
header in the past tense.ChangeLog.md
if no new release is required, such as fixing test case only.