What would you like to be added:
Each garden Linux feature can have a convert.<filetype> script that is called by the builder during the build process to convert the image.raw to something different specified in the convert.<filetype> script.
Each garden Linux feature can also have an image.<filetype> script, that is called by the builder during the build process to convert the image.tar to some other archive type.
Why is this needed:
For OCI delivery we need a mapping between mediatype and filetype. Also, the maintainer must be able to overwrite the mediatype by specifiying it in the info.yaml of the feature as entry in the oci-artifacts list. To avoid redundancy, we need to deduce the mediatype by default based only on the image and convert scripts.
What would you like to be added: Each garden Linux feature can have a
convert.<filetype>script that is called by the builder during the build process to convert the image.raw to something different specified in theconvert.<filetype>script.Each garden Linux feature can also have an
image.<filetype>script, that is called by the builder during the build process to convert the image.tar to some other archive type.Why is this needed:
For OCI delivery we need a mapping between mediatype and filetype. Also, the maintainer must be able to overwrite the mediatype by specifiying it in the info.yaml of the feature as entry in the oci-artifacts list. To avoid redundancy, we need to deduce the mediatype by default based only on the image and convert scripts.