Description:
Instead of processing JSON with meta.yaml content as list entries Unified Broker should accepts list of plugin id:version entries and download meta.yaml content from Che plugin registry.
Flow:
https://raw.githubusercontent.com/eclipse/che-plugin-registry/shareSidecarWithDebug/plugins/org.eclipse.che.vscode-redhat.java-and-xml:0.38.0 which represents https://raw.githubusercontent.com/eclipse/che-plugin-registry/shareSidecarWithDebug/plugins/org.eclipse.che.vscode-redhat.java-and-xml/0.38.0/meta.yamlDepends on https://github.com/redhat-developer/rh-che/issues/1304
Related to https://github.com/eclipse/che/issues/12908
@amisevsk Unfortunately I'm not sure that it is very clear on what exactly issue about new naming convention would involve. There are open questions about breaking existing workspaces on existing Che 7 instances, about naming convention details.
Because of that I would suggest working on this issue without taking into account changes that are supposed to be brought by that issue and we will have to adapt later. This would simplify work for you and allow us to iterate faster.
Merged upstream.
Deployed to prod