Plugin Brokers Improvements

[l0rd]

Description

We have introduced the plugin brokers to support workspace.next walking skelethon. The skeleton has been implemented and we received the first feedbacks at EclipseCon Europe. This epic is to organize the work to implement production-ready brokers that will be GA on next Che next major release (Che 7).

Tasks

• Add Unit Tests for brokers
• Brokers refactoring (remove duplicate code)
• Add the support for plugins of type VS Code Extension (registry, wsmaster and broker side) (Create VSCode extension broker for Theia #12026)
• Add sidecar image attribute in meta.yaml (part of the Create VSCode extension broker for Theia #12026)

[l0rd]

cc @garagatyi @sleshchenko @benoitf @skabashnyuk @ibuziuk @azatsarynnyy

[azatsarynnyy]

Theia should support loading a remote plugin without requiring the main process to scan of a local plugin

Currently, Theia already supports loading the remote plugins which are:

• hosted on Visual Studio Marketplace
• published as a GitHub release
• accessible by any http(s) link

@benoitf correct me if I'm wrong, please

[benoitf]

@azatsarynnyy the idea is that the .theia file should only be inside the remote container or only in volume only accessible by this theia endpoint container. Today we need to provide .theia file to the main theia container

About hosted on Visual Studio Marketplace for now it works in plain theia (with the command palette/deploy command) but we want to see as well these plug-ins from Dashboard when configuring the workspace.

[garagatyi]

@skabashnyuk FYI

[l0rd]

Opened #12392 and removed "Theia should support loading a remote plugin without requiring the main process to scan of a local plugin" from the list.

[l0rd]

Moved the non Che 7 task to #12398