Skip to content
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

Remove all CheCluster API v1 dependencies from the User Dashboard component #21594

Closed
ibuziuk opened this issue Jul 28, 2022 · 0 comments · Fixed by eclipse-che/che-dashboard#604
Assignees
Labels
area/dashboard kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system. sprint/current

Comments

@ibuziuk
Copy link
Member

ibuziuk commented Jul 28, 2022

Is your task related to a problem? Please describe

CheCluster API v1 is planned to be removed in the short run as part of - #21584

CheCluster API v2 was introduced in 7.50.0
On the last community call, we decided to deprecate CheCluster API v1 in 7.52.0 and completely remove it in 7.53.0

Required action:
All clients that use CheCluster API v1 must be updated to use CheCluster API v2.

Describe the solution you'd like

Need to make sure that https://github.com/eclipse-che/che-dashboard does not depend on CheCluster API v1
in 7.52.0 we should depend only on the v2 version

Describe alternatives you've considered

N/A

Additional context

No response

@ibuziuk ibuziuk added kind/task Internal things, technical debt, and to-do tasks to be performed. sprint/next severity/P1 Has a major impact to usage or development of the system. area/dashboard labels Jul 28, 2022
@ibuziuk ibuziuk mentioned this issue Aug 8, 2022
67 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dashboard kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system. sprint/current
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants