-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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.
Comments
This was referenced May 15, 2024
This was referenced May 22, 2024
Merged
This was referenced May 28, 2024
This was referenced Jun 4, 2024
Docs PR has not been merged yet - eclipse-che/che-docs#2738 |
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: