[Improve che-plugin.yaml] Use of the property mountProjectSources (or even the simpler mountSources) for a tool/plugin
See original GitHub issueDescription
This issue is created as result of the following discussion https://github.com/redhat-developer/devfile/pull/2#discussion_r242876449
Now if plugin developer wants to get projects sources mounted to his plugin then he has to define volume with name projects
and path /projects
.
version: 1.0.0
type: Che Editor
name: theia-ide
id: org.eclipse.che.editor.theia
endpoints:
...
containers:
- name: theia-ide
image: eclipse/che-theia:0.3.18-nightly
env:
...
volumes:
- mountPath: "/projects"
name: projects
- mountPath: "/plugins"
name: plugins
ports:
...
The idea of this issue is simplify defining of mounting projects sources to the following format:
version: 1.0.0
type: Che Editor
name: theia-ide
id: org.eclipse.che.editor.theia
endpoints:
...
containers:
- name: theia-ide
image: eclipse/che-theia:0.3.18-nightly
env:
...
volumes:
- mountPath: "/plugins"
name: plugins
mountSources: true // false
ports:
...
should define project volumes The idea of this issue is avoid defining projects volume by user/plugin developer.
The scope of this issue includes:
- Made Che Server respecting this flag and provision
projects
volume automatically with/projects
path specified. Note that the solution should be back forward compatible and plugins that are configured in old way (withprojects
volume specified) should work. It may be implemented by takingmountSources
into account only whenprojects
volume is missing; - Update field name in dockerimage tool when final name decision about
mountSources
/mountProjectSources
will be made. See https://github.com/redhat-developer/devfile/blob/master/Devfile.yaml;
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Support mountSources for non-plugin tools in devfile #12554
Implement mountSources: true/false for k8s/os component and mount projects PVC into all containers of k8s/os component. It's easy to implement ...
Read more >Introduction to Devfile - GitHub Pages
The simplest way to use devfile is to have it deployed into GitHub source repository and then create factory from this repo. This...
Read more >Re: [che-dev] Simplify mounting of project sources to plugins
Theia: it has mountSources=yes and the projects volume bound to folder /projects by default (i.e. defined in che-plugin.yaml, ...
Read more >Devfile v2 and IDE plug-ins - Eclipse Che Blog
yaml has apiVersion 1.0.0 , it will use Che server workspace engine to deploy this Devfile. If the devfile.yaml has schemaVersion 2.0.0 ...
Read more >Experimental: Configure your applications with ZAPP files - IBM
We created the new notion of a ZAPP file that describes your application in an independent representation, as YAML files as well as...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
as per https://www.eclipse.org/lists/che-dev/msg03002.html I will go ahead and create new issues for the more fine-grained tasks towards implementing the agreed solution.
Should the attribute be named
mountSources
?