Add Azure confidential VM profiles #190
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Just noticed this PR is still open. @rjschwei can we merge? |
The changes to trigger kiwi can be pulled into the PR already, see the ModifiedImages test project in IBS |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds Azure confidential VM profiles to SLES 15 SP4+ PAYG, SLES for SAP PAYG and SLES for SAP hardened PAYG.
I moved the SLES PAYG content definition for <= 15-SP3 into the SP2 and SP3 sub dirs and removed it from the SP4+ sub dirs (hence using the one in the parent dir), as this results in less duplication.
I didn't bother disabling the Azure CVM profile in SLES 4 SAP for < 15-SP4, as the extra profile doesn't interfere with the others. I can do that though in case we don't want to the profile defined for older SPs.