-
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
Support overriding Che Theia plugins preferences and sidecar through .che/che-theia-plugins.yaml #20596
Comments
Does it include supporting overriding stuff from the editor? Like memoryLimit for theia from |
This issue is only target Che theia plug-ins so not the editor |
today you can add a custom |
but https://che.eclipseprojects.io/2021/10/12/@mario.loriedo-devfile-v2-and-the-devworkspace-operator-p1.html says it's possible to override just memory for editor, and we even don't have an issue for that |
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? |
There should be new documentation for End-user guide, I think it should be done by developer who will implement this functionality. |
Is your enhancement related to a problem? Please describe
There is an issue to apply vs code extension preferences specified in the plugin registry (for che-theia plugins).
This issue is about overriding vs code extensions preferences using the file
.che/che-theia-plugin.yaml
in the git repository.Describe the solution you'd like
If the file
.che/che-theia-plugin.yaml
in the git repository exists we should use it to override the spec of the plugins.For example if the file
.che/che-theia-plugin.yaml
exist at the root of the repository:the che-theia plugin should be included in the workspace and its default preferences and sidecar specification should be merged with the one in the file.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: