3 ms·

This will get added! There is currently a lot of special casing required, as the OCI spec laying out the Registry API and interactions are not very rich. This

by gertd 5y ago

This will get added! There is currently a lot of special casing required, as the OCI spec laying out the Registry API and interactions are not very rich. This limits usability and performance. But we certainly are going to add support for ohters, ghcr.io, acr etc.

gertd 5y ago
First step was to make the explicit workflow build, tag, push, pull available for OPA while being compatible with the existing formats used by OPA. This enveloping approach, provides the workflow, explicit semantic versioning, labelling and optional signing, capabilities Step two is to make OPA natively understand and support OCI images. Next step would be special image types, and multi layering. For example I would love it if we have separate layers for rego, wasm, and data.json, as the data often needs to eleve independent of the rego and wasm code.