che
che copied to clipboard
eclipse-che
Devfile creation walkthroughs
Is your enhancement related to a problem? Please describe.
When a workspace is started and there is no Devfile in the project repository, we are not recommending to create one.
Describe the solution you'd like
We should recommend:
- To use an existing stack (a (parent) devfile from the devfile registry)
- To add container components (select image, endpoint, volumes etc...)
- To include plugins (if the editor is che-theia or vscode)
- To create and commit devfiles/extensions.json/che-theia-plugins.yaml in the project
Subtasks:
- [ ] VS Code walkthrough extension
- [ ] IntelliJ
Additional context
This work should be included in the context of che workspaces that use the DevWorkspace operator, so that's not for v1 devfiles/plugins.
Let's put this one on hold. We may want to use the devfile library that should help generating a Devfile for a given repository.
Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.
Mark the issue as fresh with /remove-lifecycle stale in a new comment.
If this issue is safe to close now please do so.
Moderators: Add lifecycle/frozen label to avoid stale mode.
Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.
Mark the issue as fresh with /remove-lifecycle stale in a new comment.
If this issue is safe to close now please do so.
Moderators: Add lifecycle/frozen label to avoid stale mode.
@l0rd @vitaliy-guliy folks, can we close the issue? extension has been published
