update to devfile 220

[yangcao77]

Signed-off-by: Stephanie yangcao@redhat.com

[kadel]

This doesn't look right. To have a proper outerloop definition you need kind: deploy command. That defines what should be executed in outerloop scenario. The way how it is written right now it would mean that all components tools, outerloop-build, outerloop-deploy should be executed on startup and application would be running in both outerloop and innerloop mode.

You should add kind: deploy command as it is in https://github.com/devfile/api/blob/main/samples/devfiles/outerloop-dockerfile-build-inlined-deploy-devfile.yaml#L99-L105

  - id: build-image
    apply:
      component: outerloop-build
  - id: deployk8s
    apply:
      component: outerloop-deploy
  - id: deploy
    composite:
      commands:
        - build-image
        - deployk8s
      group:
        kind: deploy

[benoitf]

Can we update tools container of those devfiles to use the developer image like quay.io/devfile/universal-developer-image:ubi8-d433ed6 instead of the quay.io/eclipse/che-java11-maven:nightly images that no longer exists ?

[yangcao77]

Thanks for pointing out the nightly image has been deleted. I've updated to use 7.36.0 instead. The universal developer image is huge (1.4G), and we need more discussion on whether we should switch to use that image in devfile samples. I have created an issue for that discussion, and we can talk more on that in next cabel call: devfile/api#674

I will merge the PR now to unblock the work in odc, which requires the 2.2.0 spec. We can update the samples anytime later if we decided to use another image.