What would you like to be added:
blobs that must be included in the image for a given cname can be deduced.
Creating and pushing a Garden Linux OCI image should by default work without the need to define redundantly information in the info.yaml. If a maintainer of a feature chooses to enhance information to the info.yaml, this should be respected.
Information given:
list of build artifacts (provided by the builder)
cname
version
architecture
Information that must be deduced by default:
mediatype based on filetype
Information that CAN be extended based in input from info.yaml
annotations
mediatype overwrites
exclude build artifacts
Why?
This is required by #15. We need to integrate OCI delivery without adding any extra maintenance work for the features if possible. having the current features/*/info.yaml files work without any modification greatly improves maintainability.
What would you like to be added: blobs that must be included in the image for a given cname can be deduced. Creating and pushing a Garden Linux OCI image should by default work without the need to define redundantly information in the info.yaml. If a maintainer of a feature chooses to enhance information to the info.yaml, this should be respected.
Information given:
Information that must be deduced by default:
Information that CAN be extended based in input from info.yaml
Why? This is required by #15. We need to integrate OCI delivery without adding any extra maintenance work for the features if possible. having the current features/*/info.yaml files work without any modification greatly improves maintainability.