eclipse-che
Deprecate and archive che-devfile-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
Devfile registry maintains devworkspace generator tool. This tool is used in a few places to generate DevWorkspace and DevWorkspaceTemplate objects:
- Upstream devfile registry
- Downstream devfile registry
- Che Dashboard
- Che Code
- E2E tests
- Maybe somewhere else
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 - https://github.com/eclipse-che/che/issues/23026
@tolusha @svor can I get +1 for archiving https://github.com/eclipse-che/che-devfile-registry ? I believe we can do it now
@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 @mkuznyetsov what about Che release process, should it be updated when che-devfile-registry is archived?
good point, I can archive it after the release process to avoid hiccups during the build
@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 @mkuznyetsov what about Che release process, should it be updated when che-devfile-registry is archived?
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