Abstract editor configuration as a configuration setting for admins
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
What
Currently, an editor is injected into the devfile as part of its processing. All the parameters for this editor are hardcoded in the devfile processor. This should be abstracted to a new class and exposed as a configuration that admins can set for all users to choose from. While creating a workspace, we provide a list of editors available from that group. webide will be a default entry available to all groups.
Customers should be able to provide a list of editors that can be used, and provide an image for those editors.
Why
- Adding of new editors become simple and straight forward
- Administrators can be themselves which editor their users should user; thus enabling bring-your-own-editor
- Helps administrator rollout editor upgrades/changes in a more controlled manager
Related Issues
A first iteration of this via ENV vars is implemented by Allow editor and project cloner images and tags... (#438767 - closed)