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
Regarding the user experience, here are some to-be-settled designs we need to think of:
How should user provide the name of the blob from stdin?
Besides from tar -c ...., what are the possible commands that can generate the to-be-uploaded stdin? (Asking since oras push <artifact> <folder> can already natively tar and upload the <folder> without invoking tar)
The following script is a real world example where streaming could come in handy.
Background
We fully manage the life cycle of an OpenShift cluster via a GitLab Pipeline. When creating a cluster with the openshift-install tool some files like terraform state and kube-configs will be created. Those files are needed during the whole life cycle of the cluster (not only in the current pipeline), thus they need to be stored persistently. In our case we use the existing GitLab registry and oras to create an image.
This way there is no need to create a temporary file and make sure to be in the correct directory in order to include the file without an absolute path which would make the image unable to unpack in other environments (OSs).
Are there any plans to implement this also for the input so that something like the following will be possible:
Originally posted by @ProbstDJakob in #346 (comment)
The text was updated successfully, but these errors were encountered: