You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today, to start an editor in this container, Che Dashboard through some external libs is patching entrypoint of the component.
It leads to many problems:
logic is inside dashboard side (or 3rd party library)
devfile is changed so when looking at the result it's hard to know what devfile was used as input.
entrypoint is changed
we can't use the editor without dashboard
...but I would like to have a cleaner solution where:
devfile is kept untouched
entrypoint is not overriden
it can work on top of DevWorkspaceController without any che-related stuff
So I would like to be able to define a postStart event to run a command ... but this command should be invoked in another container. (Like the first container or another one depending on one possible annotation)
TL;DR:
Add a postStart event inside the DevWorkspaceTemplate telling to execute one command in another container (but not knowing its name as the 'editor' template doesn't know much about the name of the components/containers of the devfile)
Description
Let's take the example of one simple devfile with one container
Today, to start an editor in this container, Che Dashboard through some external libs is patching entrypoint of the component.
It leads to many problems:
...but I would like to have a cleaner solution where:
So I would like to be able to define a
postStart
event to run a command ... but this command should be invoked in another container. (Like the first container or another one depending on one possible annotation)TL;DR:
Add a
postStart
event inside the DevWorkspaceTemplate telling to execute one command in another container (but not knowing its name as the 'editor' template doesn't know much about the name of the components/containers of the devfile)Additional context
It would depend on #628
DevWorkspaceTemplate would then:
The text was updated successfully, but these errors were encountered: