[AI Generated] BugFix: add SecureBoot to TrustedLaunchAndConfidentialVmSupported Linux image capabilities - #4682
Johnson (johnsongeorge-w) wants to merge 1 commit into
Conversation
0c415a5 to
e11cea5
Compare
There was a problem hiding this comment.
Pull request overview
Fixes Azure Linux image capability parsing so images advertising SecurityType=TrustedLaunchAndConfidentialVmSupported include SecureBoot in their security_profile capability set, preventing Secure Boot–requiring test cases from being incorrectly skipped.
Changes:
- Add
SecurityProfileType.SecureBootto the Linux/generic parsing path for confidential/trusted-launch capable images in_parse_security_profile.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
AI Test Case SelectionSelected 1 test case(s): smoke_test Marketplace image: Result: Succeeded |
|
Kameron Carr (@kamalca) I recalled that you ever have done some changes here, could you please review the code? Thanks. |
There was a problem hiding this comment.
Linux CVM images intentionally leave out SecureBoot because CVM Linux images are intended to be used in CVM scenarios only.
If you make this change, testing a CVM image will likely land on GP SKUs during automated testing instead of on CVM SKUs.
For Windows images there is only a single option that supports both GP and CVM scenarios. For Linux there is one image for GP scenarios and a separate image for CVM scenarios. This is the reason for treating them differently.
…VmSupported Linux image capabilities
e11cea5 to
5013228
Compare
AI Test Case SelectionSelected 1 test case(s): smoke_test Marketplace image: Result: Succeeded |
Summary
Linux images with
SecurityType=TrustedLaunchAndConfidentialVmSupportedwere missingSecureBootfrom their parsed security profile capabilities. This caused test cases requiringsecurity_profile: securebootto be skipped with:The Windows code path correctly included
SecureBootfor the same SecurityType, but the Linux/generic path only set[CVM, Stateless]. This fix addsSecurityProfileType.SecureBootto align with the Windows behavior and Azure documentation.Validation Results