Allow building and running applications at workspace start with devfile v2 post start events

[slemeur]

Description

We are now relying on devfile for the factory flow.

Factories are providing extended capabilities, allowing post-loading actions to open file, start a command.
We should be able to extend the devfile to allow a user to define those actions.

We should also make sure that users will be able to define factories with a devfile (and extended meta-datas). JSON, even if used internally by WSMaster would not be exposed anymore to the end-user.

User Stories

In the dashboard, when the user is editing the definition of a factory, it must be based on the devfile format.

• In the dashboard, a user should be able to create a factory by providing a devfile and defining the extended meta-datas.
• In the dashboard, a user should be able to create a factory from an existing workspace.

(In other words, whereever we are displaying the factory.json configuration in the dashboard, it should be replaced by devfile)

Implementation

[skabashnyuk]

@slemeur is this issue still in our GA plan? Are we going to support persistent factories in Che7 era?

[skabashnyuk]

@l0rd wdyt? can we remove GA label?

[l0rd]

@skabashnyuk removed

[matthewfisch]

What the heck team? Is this still broken? I just wasted over an hour trying to get factories working and then stumbled on this. ++ for just removing functionality that's totally broken and can't work.

So .... users can't share workspaces any other way, only copy/paste devfiles right?

[sleshchenko]

@matthewfisch In addition to copying/pasting devfiles, there is available factory flow, where users are able to host devfile somewhere, like git repo, and then just provide a link to create a workspace, like
to github repo https://che.openshift.io/f?url=http://github.com/eclipse/che
or devfile content https://che.openshift.io/f?url=https://raw.githubusercontent.com/eclipse/che/master/devfile.yaml

There is also an issue where you can track adding new feature - users devfile, in a few words - Che will allow to host devfiles for further sharing #16875.

[matthewfisch]

I am heartened that I can still use the factory flow using devfile.yaml .... but I don't understand why there's a broken factories screen. Is there any way it should work?

[veeramanikandanvv]

I am not able to create factories in eclipse che 7.17.0. I am not seeing any workspaces listed when we try to create factories out of of workspaces. Application displays error messages as - this factory is using old workspace definition. I am not able to see any documentation to update the factory runtime configuration.
Eclipse che 7.17.0, multiuser, single host.
Installed via helm on kubernetes. Please help me on this issue

[skabashnyuk]

@veeramanikandanvv persisted factories are not implemented in Che7 . Similar logic would be implemented as User devfiles #16875

[sunix]

setting back to p1.
So be able to add at least che-task and theia command to start automatically when the workspace is open

[sleshchenko]

removing dashboard and controller since it's more about devfile/v1. Once it's implemented via spec - we can think how to use that in Che Theia and Dashboard.

[che-bot]

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]

/remove-lifecycle stale

[che-bot]

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]

Should be fixed by devfile/devworkspace-operator#659