[Compute] Adding Set-AzVmUefi, Set-AzVmssUefi, Set-AzVmSecurityType, Set-AzVmssSecurityType to support Trusted Launch#14479
Conversation
|
Please add help files for these new cmdlets. |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
a4c1580 to
ce28ea6
Compare
|
@wyunchi-ms, I seem to be running into some issues with the Static Analysis portion of the pipeline, I'm not sure where it is going wrong. I've added the 4 cmdlets to the SignatureIssues.csv like I did for the PRs in the Azure-PowerShell-Pr repo but it seems like it is unable to parse the whole .csv file. |
4d6d403 to
717b124
Compare
|
You are missing the double quotes |
In my older PR in the private repo, Isra-fel said that in-memory cmdlets do not support ShouldProcess. https://github.com/Azure/azure-powershell-pr/pull/576#discussion_r502749568 The cmdlets that config a VM that support ShouldProcess are the Remove-cmdlets |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
@wyunchi-ms looks like the az pipelines pass now after fixing the SignaturesIssues.csv. Is there any chance this PR can still be included in the 3/23 release? |
It's OK for in-memory cmdlet. |
Description
Adding 4 new cmdlets to Az.Compute
Set-AzVmSecurityType
Set-AzVmUefi
Set-AzVmssSecurityType
Set-AzVmssUefi
These four cmdlets will enable customers to enable Trusted Launch on their VMs and VMSS.
Checklist
CONTRIBUTING.mdChangeLog.mdfile(s) has been updated:ChangeLog.mdfile can be found atsrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md## Upcoming Releaseheader -- no new version header should be added