-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Che-Theia Plugins view support for DevWorkspace based workspaces #20638
Comments
@vitaliy-guliy it's working as well for plug-ins with sidecars if you add their ids in .vscode/extensions.json (or in .che/che-theia-plugins.yaml) |
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? |
@max-cx I think we don't need to change any documentation |
To have the perfect UX flow we need to have
|
moving issue to 7.42 milestone as this issue is part of the endgame |
Feature has been merged. |
sync'd to Red Hat JIRA https://issues.redhat.com/browse/CRW-2748 |
Is your task related to a problem? Please describe
The existing functionality that installing a plugin adds a component to the devfile
It works only for devfile V1 workspaces, but does not work for Devfile V2 as it's completely different.
To add vscode extension to devfile V2 workspace it needs to add the extension ID to
.vscode/extensions.json
as in the examplehttps://github.com/che-samples/java-spring-petclinic/blob/devfilev2/.vscode/extensions.json
It's not a big deal for plugins, that are running in the same container withing Che-Theia. It's possible to take an extension ID or even URI (if it works) and add it to
extensions.json
.But it needs to be discusses as well what shall we do with plugins, that are running inside separate container.
Describe the solution you'd like
Find a way to install a plugin from
che-pluin-registry
to devfile V2 workspace.Release Notes Text
Che-Theia now supports plugins management from the built-in Plugin View for DevWorkspace based workspaces as well.
The text was updated successfully, but these errors were encountered: