Skip to content

Enable trusted launch for existing-WVD-host-pool-arm - #656

Open
aprillc wants to merge 2 commits into
masterfrom
z/aprilcai/host4
Open

Enable trusted launch for existing-WVD-host-pool-arm#656
aprillc wants to merge 2 commits into
masterfrom
z/aprilcai/host4

Conversation

@aprillc

@aprillc aprillc commented Nov 2, 2021

Copy link
Copy Markdown

Add three trusted launch parameters for the ARM template.

@philipktlin

Copy link
Copy Markdown
Contributor

@aprillc

aprillc commented Nov 3, 2021

Copy link
Copy Markdown
Author

@aprillc aprillc closed this Nov 3, 2021
@aprillc aprillc reopened this Nov 3, 2021
@aprillc

aprillc commented Nov 3, 2021

Copy link
Copy Markdown
Author

clicked wrong button

@aprillc

aprillc commented Nov 3, 2021

Copy link
Copy Markdown
Author

},
"defaultValue": ""
},
"securityType": {

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These parameters aren't passed to the virtual machine so it doesn't do anything.

},
"defaultValue": ""
},
"securityType": {

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These parameters aren't passed to the virtual machine so it doesn't do anything.

},
"defaultValue": {}
},
"securityType": {

@lintFan lintFan Nov 3, 2021

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If the only valid value for this is an empty string or TrustedLaunch then you should specify "allowedValues" with those values so the customer will get an error if they enter something else.
This applies to the other ARM templates in this PR too.

"secureBoot": {
"type": "bool",
"metadata": {
"description": "Specifies whether secure boot should be enabled on the virtual machine."

@lintFan lintFan Nov 3, 2021

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should say this is only used if securityType is set to "TrustedLaunch".
This applies to the other ARM templates in this PR too.

"vTPM": {
"type": "bool",
"metadata": {
"description": "Specifies whether vTPM (Virtual Trusted Platform Module) should be enabled on the virtual machine."

@lintFan lintFan Nov 3, 2021

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should say this is only used if securityType is set to "TrustedLaunch".
This applies to the other ARM templates in this PR too.

"securityType": {
"type": "string",
"metadata": {
"description": "Specifies the SecurityType of the virtual machine. It is set as TrustedLaunch to enable UefiSettings. Default: UefiSettings will not be enabled unless this property is set as TrustedLaunch."

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would be helpful to include a link to the docs for this here https://docs.microsoft.com/en-us/azure/templates/microsoft.compute/2021-07-01/virtualmachines?tabs=bicep#securityprofile so the customer has more context about this.

@lintFan

lintFan commented Nov 3, 2021

Copy link
Copy Markdown
Member

Would you please help to remove https://github.com/Azure/RDS-Templates/blob/master/ARM-wvd-templates/nestedtemplates/unmanagedDisks-customvhdvm.json? thanks.

Removed.

It looks like unmanagedDisks-customvhdvm.json is still supported in AddVirtualMachinesTemplate.json and CreateHostpoolTemplate.json . If you want to remove support for it then I suggest taking a look at this PR https://github.com/Azure/RDS-Templates/pull/406/files where WVD classic removed support for it. You may also want to announce it as an upcoming breaking change to customer before making the change too. Although it was announced here (I think before the non-classic templates were released) so it might be ok.

This also seems un-related to the other changes in this PR so maybe make an changes around unmanagedDisks-customvhdvm.json in a separate PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants