Allow to specify 'latest' version of plugins in workspaces definitions

[l0rd]

Description

Although it's important to be able to specify a particular version of a plugin/editor to be included in a workspace or stack, in most cases we just need latest version.

This issue is to allow a definition of a workspace plugin without a specific version:

id: che-machine-exec-plugin

and with version latest:

id: che-machine-exec-plugin:latest

This should work for devfiles, workspaces json and stacks.

Subtasks created:

• Need to create the latest folder for each plugin in the plugin registry that would allow to specify plugins with the latest version redhat-developer/rh-che#1395
• If the plugin version is not specified - fall back on latest  redhat-developer/rh-che#1396

[ibuziuk]

A potential solution is to create "latest" folder which would always duplicate the highest version of the plugin

[ibuziuk]

@l0rd am I correct that plugin without version e.g. id: che-machine-exec-plugin = latest ?

[l0rd]

Yes you are correct

[ibuziuk]

For me, it looks like a relatively simple issue that can be delivered in the 2 steps manner (and even split into two issues):

• id: che-machine-exec-plugin:latest case can be solved by the creation and a requirement for all v2 plugin always having the latest folder with the dedicated content (chagnes) - estimate (1-2 sp.)
• id: che-machine-exec-plugin case should be tackled on wsmaster / plugin broker side (when version is missing always fall back on the latest) - estimate (3p.)

@l0rd does this sound like a good plan? If yes, I would create 2 dedicated rh-che issues for the next sprint planning.

[l0rd]

@ibuziuk yes that looks like a good plan. Another thing you need to take care of are the versions of the exec and theia that are automatically added by wsmaster (when a user do not specify them in a Devfile). You should probably use version 'latest' for both and it could be part of the first task.

[ibuziuk]

Subtasks created:

• Need to create the latest folder for each plugin in the plugin registry that would allow to specify plugins with the latest version redhat-developer/rh-che#1395
• If the plugin version is not specified - fall back on latest  redhat-developer/rh-che#1396

[amisevsk]

A PR for latest folders is here: eclipse-che/che-plugin-registry#143, but I don't know if this is the direction we want to go in. Ideally the plugin registry is more than a httpd server and can return the latest version by itself -- manually maintaining latest dirs in the registry could be error-prone.

[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.

[amisevsk]

Closing as the core issue here is out of date. Latest folders are included in the plugin registry now.