[Compute] Adding Set-AzVmUefi, Set-AzVmssUefi, Set-AzVmSecurityType, Set-AzVmssSecurityType to support Trusted Launch

[sf-76]

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

• I have read the Submitting Changes section of CONTRIBUTING.md
• The title of the PR is clear and informative
• The appropriate ChangeLog.md file(s) has been updated:
  • For any service, the ChangeLog.md file can be found at src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
  • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header -- no new version header should be added
• The PR does not introduce breaking changes
• If applicable, the changes made in the PR have proper test coverage
• For public API changes to cmdlets:
  • a cmdlet design review was approved for the changes in this repository (Microsoft internal only)
    • https://github.com/Azure/azure-powershell-cmdlet-review-pr/issues/867
    • https://github.com/Azure/azure-powershell-cmdlet-review-pr/issues/866
    • https://github.com/Azure/azure-powershell-cmdlet-review-pr/issues/735
    • https://github.com/Azure/azure-powershell-cmdlet-review-pr/issues/695
  • the markdown help files have been regenerated using the commands listed here

[wyunchi-ms]

Please add help files for these new cmdlets.

[wyunchi-ms]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[sf-76]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[sf-76]

@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.

[wyunchi-ms]

You are missing the double quotes ".
And I think ShouldProcess is necessary. Could you please support it?

[sf-76]

You are missing the double quotes ".
And I think ShouldProcess is necessary. Could you please support it?

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

[sf-76]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[sf-76]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[sf-76]

@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?

[wyunchi-ms]

You are missing the double quotes ".
And I think ShouldProcess is necessary. Could you please support it?

In my older PR in the private repo, Isra-fel said that in-memory cmdlets do not support ShouldProcess. Azure/azure-powershell-pr#576 (comment)

The cmdlets that config a VM that support ShouldProcess are the Remove-cmdlets

It's OK for in-memory cmdlet.