Allow to expose more metadata like the cloud-workspace metadata through plug-in

[benoitf]

Hello,

Within Eclipse Che, we're interested in using this registry. One limitation is that for some extensions, we need to specify the OCI image to use. It also includes some extra information like the memory or cpu to allocate.

After some discussions, it seems we could then package the metadata (currently a meta.yaml) file inside the vsix. Then, the metadata could be extracted when we submit vsix file and then stored in the registry. Thus, registry endpoint could serve the meta yaml file when asking for it.

We would need as well to display on the UI part this kind of information stored in the meta.yaml.

That said, we agree that this kind of information is optional as it might not interest at all people wanted only to use the registry with VS Code for example.

Compromise seems that to provide this logic through a 'plug-in'.

'Cloud Eclipse Che plug-in' would

• allow to extract/store more data when submitting vsix files
• add UI part reusing this extracted information

So extra logic is done in a plug-in that can be installed or not on top of the registry

[amvanbaren]

Hi @benoitf, Open VSX now has a /vscode/unpkg endpoint. This endpoint is used by VS Code as resourceUrlTemplate, but it could also be used to access the meta.yaml file. Would this work for you?

NOTE: the current version running at open-vsx.org doesn't have the /vscode/unpkg endpoint yet. https://github.com/eclipse/openvsx/blob/df28c16c4d919afaf1c8795ab0dfabd842ceb6e6/server/src/main/java/org/eclipse/openvsx/adapter/VSCodeAdapter.java#L385-L402

I don't quite get why Open VSX needs to visualize the extracted information. Wouldn't it be better to show this in Che?

[amvanbaren]

cc @nickboldt

[nickboldt]

cc: @svor @l0rd