You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/Compute/Compute.Test/SessionRecords/Microsoft.Azure.Commands.Compute.Test.ScenarioTests.ImageTests/TestDefaultImagesExistManual.json
Copy file name to clipboardExpand all lines: src/Compute/Compute/ChangeLog.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,6 +27,9 @@
27
27
* Added 'MaxSurge' to Set-AzVmssRollingUpgradePolicyCommand
28
28
* Added support for 'latest' in 'Get-AzvmImage' '-Version' parameter
29
29
* Added `CompletionPercent` property to PSDisk object.
30
+
* Removed the image alias `CoreOS` as the publisher CoreOS no longer has any images for Azure.
31
+
Updated the names of the `openSUSE-Leap` and `SLES` aliases to `OpenSuseLeap154` and `SuseSles15SP4` respectively. Updated these aliases to point to an image that actually exists and updated the alias names to be descriptive and versioned.
32
+
* Added new descriptive and versioned alias names for the Linux image aliases.
30
33
31
34
## Version 5.4.0
32
35
* Added `-SkipIdentity`, `-PathUserIdentity`, `-IsTest` parameter to `Set-AzVMAEMExtension`
Copy file name to clipboardExpand all lines: src/Compute/Compute/VirtualMachine/Operation/NewAzureVMCommand.cs
+8-4Lines changed: 8 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -54,7 +54,8 @@
54
54
55
55
namespaceMicrosoft.Azure.Commands.Compute
56
56
{
57
-
[GenericBreakingChange("Starting in May 2023 the \"New-AzVM\" cmdlet will deploy with the Trusted Launch configuration by default. To know more about Trusted Launch, please visit https://learn.microsoft.com/en-us/azure/virtual-machines/trusted-launch")]
57
+
[GenericBreakingChange("Consider using the image alias including the version of the distribution you want to use in the \"-Image\" parameter of the \"New-AzVM\" cmdlet. On April 30, 2023, the image deployed using `UbuntuLTS` will reach its end of life. ")]
58
+
[GenericBreakingChange("Starting in May 2023 the \"New-AzVM\" 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")]
58
59
[GenericBreakingChange("It is recommended to use parameter \"-PublicIpSku Standard\" in order to create a new VM with a Standard public IP.Specifying zone(s) using the \"-Zone\" parameter will also result in a Standard public IP.If \"-Zone\" and \"-PublicIpSku\" are not specified, the VM will be created with a Basic public IP instead.Please note that the Standard SKU IPs will become the default behavior for VM creation in the future")]
This example Creates a new VM as part of a VMSS with a PlatformFaultDomain value.
252
+
This example creates a new VM as part of a VMSS with a PlatformFaultDomain value.
253
253
254
254
### Example 7: Creating a new VM with the GuestAttestation extension installed by default, then recreating the VM with DisableIntegrityMonitoring to prevent this.
# This VM does not have the Guest Attestation extension installed on it, and the Identity is not set to SystemAssigned by default.
316
316
```
317
317
318
-
This example Creates a new VM with the GuestAttestation extension installed by default, then recreating the VM with DisableIntegrityMonitoring to prevent this.
318
+
This example creates a new VM with the GuestAttestation extension installed by default, then recreating the VM with DisableIntegrityMonitoring to prevent this.
319
+
320
+
### Example 8: Create a VM using the -Image alias.
The friendly image name upon which the VM will be built. These include: Win2022AzureEditionCore, Win2019Datacenter, Win2016Datacenter, Win2012R2Datacenter, Win2012Datacenter, UbuntuLTS, CentOS, CoreOS, Debian, openSUSE-Leap, RHEL, SLES.
689
+
The friendly image name upon which the VM will be built. The available aliases are: Win2022AzureEditionCore, Win2019Datacenter, Win2016Datacenter, Win2012R2Datacenter, Win2012Datacenter, UbuntuLTS, Ubuntu2204, CentOS, CentOS85Gen2, Debian, Debian9, OpenSuseLeap154, RHEL, RHELRaw91Gen2, SuseSles15SP4.
Copy file name to clipboardExpand all lines: tools/StaticAnalysis/Exceptions/Az.Compute/ExampleIssues.csv
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -17,3 +17,4 @@
17
17
"Az.Compute","Set-AzVMSecurityProfile","2","26","Capitalization_Conventions_Violated","5101","1","Set-AzVmSecurityProfile doesn't follow the Capitalization Conventions.","Set-AzVmSecurityProfile -VM $VirtualMachine -SecurityType $SecurityType","Check the Capitalization Conventions. Suggest format: Set-AzVMSecurityProfile"
18
18
"Az.Compute","Set-AzVMSecurityProfile","2","27","Capitalization_Conventions_Violated","5101","1","Set-AzVmUefi doesn't follow the Capitalization Conventions.","Set-AzVmUefi -VM $VirtualMachine -EnableVtpm $true -EnableSecureBoot $true","Check the Capitalization Conventions. Suggest format: Set-AzVMUefi"
19
19
"Az.Compute","Set-AzVMSecurityProfile","2","33","Capitalization_Conventions_Violated","5101","1","Get-AzVm doesn't follow the Capitalization Conventions.","Get-AzVm -ResourceGroupName $rgname -Name $vmname","Check the Capitalization Conventions. Suggest format: Get-AzVM"
20
+
"Az.Compute","New-AzVM","8","9","Invalid_Cmdlet","5000","1","New-AzResourceGroup is not a valid command name.","New-AzResourceGroup -Name $rgname -Location $loc -Force","Check the spell of New-AzResourceGroup."
0 commit comments