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
Walking skeleton epic describes that we need an ability to deliver ChePlugins binaries to a che editor sidecar container. This would allow us, for example, to have a dynamic pluggability in Che Theia.
There might be different ways to deliver those binaries, so we need to investigate options and implement at least one of them for the walking skeleton POC.
Delivering options:
Usage of data containers that don't run any process but pulled from a registry and mount some folder to another container (editor container)
Download binaries from a marketplace (for now it is just an Apache server)
Usage of init container in kubernetes
We might also think about ChePlugins owners being able to use different mechanisms (described here or others) depending on their needs but this is not needed for a POC and it might complicate the flow, so having just one mechanism seems more natural for me for the time being.
Add a plugin downloader component in wsmaster that
Get as input the workspace config list of plugins and editor
Downloads the plugins and editor files (*.tar.gz and *.theia) from the plugin registry
Extract the tar.gz in che-plugins and che-editor folders
Copies *.theia files in a theia-plugins folder
Returns the local paths to the che-plugin.yml and che-editor.yml files
Add an editor plugin injector component in wsmaster that copies the content of editor plugins folder (theia-plugins) in the volume that will be mounted in the theia container
The text was updated successfully, but these errors were encountered:
Description
Walking skeleton epic describes that we need an ability to deliver ChePlugins binaries to a che editor sidecar container. This would allow us, for example, to have a dynamic pluggability in Che Theia.
There might be different ways to deliver those binaries, so we need to investigate options and implement at least one of them for the walking skeleton POC.
Delivering options:
We might also think about ChePlugins owners being able to use different mechanisms (described here or others) depending on their needs but this is not needed for a POC and it might complicate the flow, so having just one mechanism seems more natural for me for the time being.
Subtasks:
*.tar.gz
and*.theia
) from the plugin registryche-plugins
andche-editor
folders*.theia
files in atheia-plugins
folderche-plugin.yml
andche-editor.yml
filesThe text was updated successfully, but these errors were encountered: