Skip to content

[devfile-registry] Rework the devworkspace generation process #21831

@svor

Description

@svor

Is your task related to a problem? Please describe

For now we are using libraries to generate DevWorkspaces with Theia and VS Code editor, once devfile/devworkspace-operator#939 was merged, DevWorkspaces support a new field .spec.contributions.

When generating devworkspaces during the build of the devfile registry, editors/other components should be injected into contributions field:

 apiVersion: workspace.devfile.io/v1alpha2
 kind: DevWorkspace
 metadata:
   name: golang-example
   namespace: <username>-che
 spec:
   routingClass: che
   started: false
   contributions:
+    - name: theia
+      kubernetes:
+        name: che-code-workspace1cfc13df8bcf497a
+        namespace: <username>-che
   template:
     components:
       - name: tools
         container:
           image: udi8
           # etc
-      - name: theia
-        plugin:
-          kubernetes:
-            name: che-code-workspace1cfc13df8bcf497a
-            namespace: <username>-che

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/devfile-registryarea/sampleskind/enhancementA feature request - must adhere to the feature request template.severity/P1Has a major impact to usage or development of the system.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions