Problem:

Goal:

Better align back end implementation of ODC, odo & OpenShift Connector around Import from Git, and location the devfile in the git repo.

Why is it important?

• Cross portfolio consistency

Acceptance criteria:

1. For devfile which has resource URI, UI need to send inline yaml to backend api: devfile backend will always return Deployment, BuildConfig and ImageStream. If Service and Endpoint/Route are defined in the devfile, backend will return those resources otherwise it will not.
2. For devfile which has no URI or inline is not set in devfile itself : devfile backend will return Deployment, BuildConfig, ImageStream, Service and Route like the master branch (but it is not getting this data from the YAML)

• FYI: Other Kube resources like CronJob defined in the devfile YAML (uri/inline) will be ignored by backend at the moment. We can discuss this in the future,  if we want to improve on our current implementation including having multiple Deployments, Services, Routes, etc.. (This we need to plan for 4.13)

Dependencies (External/Internal):

Need to talk to eyuen@redhat.com to determine what the dependencies are in order to implement this.

Design Artifacts:

Exploration:

Note: