Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-2550

Support v2 devfiles with che-server by converting them into corresponding v1 devfiles

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Major
    • 2.13.0.GA
    • 2.14.0.GA
    • docs
    • False
    • False
    • Hide
      = All workspace engines support devfile v2

      With this update, {prod-short} supports creating workspaces from a devfile version 2 on all workspace engines. Before this update, using the {devworkspace} engine was required.
      Show
      = All workspace engines support devfile v2 With this update, {prod-short} supports creating workspaces from a devfile version 2 on all workspace engines. Before this update, using the {devworkspace} engine was required.

    Description

      Synced from Eclipse Che issue

      https://github.com/eclipse/che/issues/20644

      Is your task related to a problem? Please describe

      That's important because Che and CRW don't get devfile v2 support(devworkspace mode) by default, but OpenShift Console already use them for default samples and it breaks integration.

      <img width="1269" alt="image" src="https://user-images.githubusercontent.com/606959/136627809-e276f80f-31a7-42be-93b2-e503581343ad.png">

      Describe the solution you'd like

      Che should supply devfile v2 in Che Server mode (by converting it to devfile v1).

      It includes the following subtasks:

      :notebook: dashboard won't validate generated devfile v1 (from devfile v2) against devfile v1 schema, and if there is any bug in conversion logic, the user will get an unclear message that some component is not a valid or field is missing, but in a fact there is nothing user can do with that.

      Release Notes Text

      Che now supports creating workspaces from a Devfile that uses v2 of the spec even if the workspace engine is the che-server (the current default). Previously that was possible only if Che was configured with the DevWorkspace operator as workspace engine.

      Attachments

        Activity

          People

            Unassigned Unassigned
            jiralint.codeready Bot Codeready
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: