-
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
Deprecate and archive che-devfile-registry #22960
Comments
Devfile registry maintains devworkspace generator tool. This tool is used in a few places to generate DevWorkspace and DevWorkspaceTemplate objects:
So, this tool should be moved to another place with all related GH actions: https://github.com/eclipse-che/che-devfile-registry/tree/main/.github/workflows |
@tolusha @olexii4 @akurinnoy please, review the proposal - #23026 |
@tolusha @svor can I get +1 for archiving https://github.com/eclipse-che/che-devfile-registry ? I believe we can do it now |
+1 from me |
good point, I can archive it after the release process to avoid hiccups during the build |
right, che-release must be updated to not trigger che-devfile-registry release workflow anymore. |
opened https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4904 since I do not have permission for archiving the registry |
Is your task related to a problem? Please describe
Eclipse Che is using devfile.io by default starting from 7.82.0 - https://github.com/eclipse-che/che/releases/tag/7.82.0
We can now deprecate and archive - https://github.com/eclipse-che/che-devfile-registry + related samples
Describe the solution you'd like
Since devfile.io is used by default we can deprecate and archive https://github.com/eclipse-che/che-devfile-registry
As part of this exercise, we should also archive https://github.com/che-samples which we are not going to support anymore
Describe alternatives you've considered
No response
Additional context
In terms of downstream, we should replace getting-started samples with CM approach that operator would be managing - https://access.redhat.com/documentation/en-us/red_hat_openshift_dev_spaces/3.13/html/administration_guide/configuring-devspaces#configuring-getting-started-samples
tricky part is air-gap, and we need to find a solution for it
The text was updated successfully, but these errors were encountered: