Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Request to support --enable-integrity-monitoring flag with security type 'ConfidentialVM' #30516

Open
1 task done
ketanatri1 opened this issue Dec 13, 2024 · 2 comments · May be fixed by #30690
Open
1 task done

Request to support --enable-integrity-monitoring flag with security type 'ConfidentialVM' #30516

ketanatri1 opened this issue Dec 13, 2024 · 2 comments · May be fixed by #30690
Assignees
@zhoxing-ms @yanzhudd
Labels
Auto-Assign Auto assign by bot Azure CLI Team The command of the issue is owned by Azure CLI team Compute az vm/vmss/image/disk/snapshot customer-reported Issues that are reported by GitHub users external to the Azure organization. feature-request
Milestone
Backlog

Comments

@ketanatri1
Copy link

Preconditions

  • No need to upgrade Python SDK or the Python SDK is ready.

Related command

az vm create
az vmss create

Resource Provider

Microsoft.Compute/virtualMachines/extensions

Description of Feature or Work Requested

Current Az CLI supports the flag '--enable-integrity-monitoring' when '--security-type' for VM is set to 'TrustedLaunch'.
This flag causes the Guest attestation extension to be installed on the VM.
More details on the flag and its usage can be found here: https://learn.microsoft.com/en-us/azure/virtual-machines/boot-integrity-monitoring-overview?tabs=cli

We would like to add the same usage of this flag for '--security-type' 'ConfidentialVM' as well. This way the Guest attestation extension will be installed for Confidential VMs as well when the flag is used with the az vm create or az vmss create command.

Minimum API Version Required

N/A

Swagger PR link / SDK link

N/A

Request Example

No response

Target Date

2025-01-15

PM Contact

reprasa, tusharjain

Engineer Contact

ketanatri, babnishvyas

Additional context

No response
@yonzhan
Copy link
Collaborator

yonzhan commented Dec 13, 2024

Thank you for opening this issue, we will look into it.

@microsoft-github-policy-service microsoft-github-policy-service bot added customer-reported Issues that are reported by GitHub users external to the Azure organization. Compute az vm/vmss/image/disk/snapshot labels Dec 13, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added Auto-Assign Auto assign by bot Azure CLI Team The command of the issue is owned by Azure CLI team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Dec 13, 2024
@yonzhan yonzhan removed the question The issue doesn't require a change to the product in order to be resolved. Most issues start as that label Dec 13, 2024
@yonzhan yonzhan added this to the Backlog milestone Dec 13, 2024
@yanzhudd yanzhudd linked a pull request Jan 22, 2025 that will close this issue
Open
3 tasks
@yanzhudd
Copy link
Contributor

Hi @ketanatri1
could you please help verify if this private package could meet your expectations?
You can refer to this guideline. Thanks!

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

@zhoxing-ms zhoxing-ms

@yanzhudd yanzhudd

Labels
Auto-Assign Auto assign by bot Azure CLI Team The command of the issue is owned by Azure CLI team Compute az vm/vmss/image/disk/snapshot customer-reported Issues that are reported by GitHub users external to the Azure organization. feature-request
Projects
None yet
Milestone
Backlog
4 participants
@zhoxing-ms @yonzhan @yanzhudd @ketanatri1