-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extend the DevWorkspaceTemplate spec with containers contributions #656
Closed
Comments
1 task
sleshchenko
added
sprint/current
Is assigned to issues which are planned to work on in the current team sprint
and removed
sprint/next
labels
Oct 28, 2021
amisevsk
added
sprint/next
and removed
sprint/current
Is assigned to issues which are planned to work on in the current team sprint
labels
Nov 5, 2021
ibuziuk
added
sprint/current
Is assigned to issues which are planned to work on in the current team sprint
and removed
sprint/next
labels
Nov 10, 2021
ibuziuk
changed the title
Investigate an ability to inject stuff(volume, env var, postStart command) into user's container
[SPIKE] Investigate an ability to inject stuff(volume, env var, postStart command) into user's container
Nov 10, 2021
Hi, a question to the assignee of this issue: Will the outcome require any changes to the relevant content of the Installation Guide or Administration Guide or End-user Guide? Yes/No? |
ibuziuk
added
sprint/next
and removed
sprint/current
Is assigned to issues which are planned to work on in the current team sprint
labels
Feb 8, 2022
l0rd
changed the title
[SPIKE] Investigate an ability to inject stuff(volume, env var, postStart command) into user's container
Support containerContribution component type to inject stuff(volume, env var, postStart command) into user's container
Feb 20, 2022
41 tasks
l0rd
changed the title
Support containerContribution component type to inject stuff(volume, env var, postStart command) into user's container
Extend the DevWorkspace spec with containers contributions
Apr 27, 2022
l0rd
changed the title
Extend the DevWorkspace spec with containers contributions
Extend the DevWorkspaceTemplate spec with containers contributions
Apr 27, 2022
9 tasks
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Che Editors (VS Code, Theia, JetBrain IDEs) are defined as
DevWorkspaceTemplate
. But theDevWorkspaceTemplate
syntax currently lacks a way to express the changes required to the containers that will host the editor. In fact Che Editors are injected in user's containers (which one is covered here) and require changes to the original user's container to work properly: add env variables, volumes, mem and cpu requisites, postStart and postStart events etc...This feature is critical to allow using the same Devfile or DevWorkspace with different editors. But also to unblock some other features as "universal" idling.
This is a subtask of eclipse-che/che#21340
Here is an example of a
DevWorkspaceTemplate
that defines VS Code with acontainerContribution
component:VS Code editor definition:
And here is a DevWorkspace that references the previous DWT:
This should be the resulting flattened DevWorkspace:
env
,endpoints
andvolumeMounts
are appended to user DevWorkspaceThe text was updated successfully, but these errors were encountered: