Decouple editor definitions from the plugin registry #22932
Labels
area/che-operator
Issues and PRs related to Eclipse Che Kubernetes Operator
area/plugin-registry
kind/task
Internal things, technical debt, and to-do tasks to be performed.
kind/technical-debt
Technical debt issue
severity/P2
Has a minor but important impact to the usage or development of the system.
Is your task related to a problem? Please describe
Currently, plugin registry contains both plugins and editor definitions https://github.com/eclipse-che/che-plugin-registry
which breaks single-responsibility principle.
What is more even if internal plugin registry is not used e.g.
The operand is still there for hosting editor definitions - https://github.com/eclipse-che/che-plugin-registry/blob/main/che-editors.yaml
plugin-registry operand is running and consuming resources only for hosting a single yaml file
Describe the solution you'd like
use cm for editor definitions similar to #22429
Describe alternatives you've considered
let UD handle hosting of editor definitions
Additional context
No response
The text was updated successfully, but these errors were encountered: