You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The more we talk about this internally, the more it seems like that could make sense.
There are downsides to this approach (namely that we can't modify/transform your code at the registry layer, all modifications have to happen locally before you push to the registry).
At the same time, we gain access to the myriad of OCI-compliant registries.
It's a nuanced issue, and I think the best thing to do is wait until the Signatures V1 release (which is coming soon, join our discord!) and then once we have enough users of that we can have a proper community meeting to make a decision on this.
+1 to wanting OCI-compatible registry support. It would allow to easier adoption in a corporate setting. I would even prefer to run modifications locally.
Acceptance Criteria
scale fn oci-push
existsscale fn oci-pull
existsQuestions
How could we pass function params and get the appropriate output from the registry?.tar.gz
file that gets pushed to the registry.Would the OCI include the runner?The text was updated successfully, but these errors were encountered: