tektoncd/pipeline

Binary (local) input type

Ouverte

#924 ouverte le 29 mai 2019

 (11 commentaires) (5 réactions) (0 personne assignée)Go (1 943 forks)auto 404
designhelp wantedkind/designkind/questionlifecycle/frozen

Métriques du dépôt

Stars
 (9 013 étoiles)
Métriques de merge PR
 (Merge moyen 9j 3h) (137 PRs mergées en 30 j)

Description

Openshift builds have a really neat concept of Binary (local) sources. Essentially, it gives you an API to stream binary contents into a build from anywhere (including the local file system).

This opens the door for nice FaaS-style user-experiences, where the user might want to do something like cli create my-large-packaged-nodejs-function.zip, then expect this to be build into a container image and ultimately that image then being pushed to run somewhere (for example Knative Serving).

This flow would be possibly without requiring the user to push this code somewhere and without the user having to install software to build and manage images.

Would that be something that Tekton could support?

Guide contributeur