[WIP] Draft proposal for new image tomls#16184
Draft
realsdx wants to merge 2 commits intotomls/base/mainfrom
Draft
[WIP] Draft proposal for new image tomls#16184realsdx wants to merge 2 commits intotomls/base/mainfrom
realsdx wants to merge 2 commits intotomls/base/mainfrom
Conversation
32b5986 to
4df7dfd
Compare
This file contains hidden or 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
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 PR proposes extending Azure Linux image definitions with delivery metadata so they can be consumed by TEE.
As part of that,
images.tomlis changed to a thin include based registry and image definitions are moved into per-image*.image.tomlfiles alongside their KIWI definitions. The new manifest shape introduces fields such as name, distro, delivery, and variants so image delivery mechanisms and constraints can be defined closer to the image itself.Scope: Introduce image delivery definitions
*means this field is intentionally unresolved in the manifest and must be filled in by a later delivery, publish, or fulfillment step. The key is still declared here so downstream tooling knows the field exists and can provide or validate it.Note: It has not been verified with azldev. Runtime support in azldev is still needed for the new image fields.