Open johnmcollier opened 5 years ago
Marking as a tech-topic since there's a number of architectural changes that need to be discussed as a whole before we decide on this
Also adding area/vscode-ide
as this will require a few changes to the Theia extension.
Cleaning up issues right now, since this has been put on hold, can you re-add the vs code label or open a new issue once the iterative dev component is finished?
We currently have two separate Che plugins required for Codewind to function:
codewind-theia
for the Codewind Theia/VS Code extensioncodewind-sidecar
for the PFE deployment, reverse proxy, and file watching.This means that if a user wants to start a Codewind workspace in Che, they need to ensure that both plugins are installed into the workspace, which is usually done by creating a special workspace from one of our devfiles. It also means we have to maintain two Che plugins (including an entire container!), it isn't straightforward for a user to install Codewind in an existing workspace, and we don't have a way to easily 'restart' PFE.
Instead, we should look at consolidating the Che plugins into one single Che plugin. This would mean deprecating the
codewind-che-sidecar
container and offloading its responsibilities to the Theia extenstion. This would: 1) Allow us to produce a single Che plugin for Codewind that users can easily install into their Che workspaceToDo: