Should we look at easing up the pack.content.images validation given that there are use-cases where users either create packs that do not have container images OR they don't actually need/want to have pack.content.images as part of their pack building flow/process.
Should we create a WARN instead of throwing an ERR and breaking the validation altogether?
Should we look at easing up the pack.content.images validation given that there are use-cases where users either create packs that do not have container images OR they don't actually need/want to have pack.content.images as part of their pack building flow/process.
Should we create a WARN instead of throwing an ERR and breaking the validation altogether?