Use of "registry.devfile.io" devfile registry

[benoitf]

Is your task related to a problem? Please describe.

Che has a devfile registry since Che 7.x and devfile v1 and the devfile registry is providing the stacks/examples.

In the meantime, devfile that has been incubated in Che is now developed as a separate organization at https://github.com/devfile

For devfile v2, devfile people have developed a new OCI registry having REST api on top of it: https://registry.devfile.io/viewer

Describe the solution you'd like

• As a first iteration continue using che devfile registry:
  • Support v2.2 Devfiles #20850
  • Check that workspaces start successfully with OCP 4.10 Console samples #21063
  • Che devfile registry build should fetch samples from devfile.io #20034
  • Handle gracefully when an invalid devfile is found in a git repository #20738
• DevWorkspace Operator and IDE issues to support registry devfiles
  • When a devfile references a parent we should not add the default component #22103
  • starterProjects support devfile/devworkspace-operator#1084
  • Editor is not started when workspace started from some devfiles from the registry.devfile.io #22525
  • It is not possible to start a terminal when workspace started from a devfile from the registry.devfile.io #22524
  • Create acceptance tests to go through all devfile samples and all editors using API #21514
  • Ensure devfiles available on the registry are compatible with devworkspace devfile/api#681
  • Support running VS Code in the containers that don't include the pre-requisites #21778
  • When a devfile starterProject is used the $PROJECT_SOURCE variable is misconfigured #22601
• Che Dashboard and Operator issues to consume the new registry
  • As an Admin, I want to enable registry.devfile.io in CR on demand, and see all the devfiles as Getting Started samples on the User Dashboard #22142
  • Use 'registry.devfile.io' by default in Eclipse Che #22485
  • Use the first 'starterProject' during DevWorkspace creation from devfile.io samples / stacks #22486
• Devfile registry issues:
  • Not possible to deploy the devfile registry via CR on OpenShift 4.12 devfile/api#1092
  • OperatorHub availability
    • Make Registry operator available on operatorhub.io and in Operator catalog devfile/api#1007
    • Put devfile registry operator to OperatorHub devfile/api#410
  • Devfile registry air gap/offline installation devfile/api#329
• Fill the feature gap (not a blocker to switch to registry.devfile.io)
  • In project starters add .vscode/extensions.json, .vscode/launch.json as needed
  • Define$DEBUG_PORT where needed
  • Set exposure:none for the debug endpoint

[l0rd]

Issue on the devfile org side to make those devfiles compatible with Che devfile/api#681 (the list of problems is in this comment).

This is related to odo and che different interpreations of the Devfile 2.x.

[ibuziuk]

Closing the epic. Starting from 7.82.0 Eclipse Che is going to use registry.devfile.io by default