-
Notifications
You must be signed in to change notification settings - Fork 5
Conversation
Codecov Report
@@ Coverage Diff @@
## main #165 +/- ##
=====================================
Coverage 4.93% 4.93%
=====================================
Files 12 12
Lines 2899 2899
=====================================
Hits 143 143
Misses 2732 2732
Partials 24 24 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you please elaborate more why it was decided to disable it but not fix it?
@oksana-grishchenko The main goal from the product standpoint for the CLI is the provisioning/unprovisioning of Everest. Right now, the list command returns only versions and database engines which IMO does not provide any value for the user in comparison to the UI. Another point that to fix it completely we need to add filtration by cluster name for list kubernetes endpoint to provide the end user an ability to use cluster name as an identifier to list different resources |
CHANGE DESCRIPTION
Problem:
EVEREST-358
Short explanation of the problem.
The main goal from the product standpoint for the CLI is the provisioning/unprovisioning of Everest.
Currently, there's no way of getting kubernetes-id using CLI because the end user needs to call http://everest-backend:8080/v1/kubernetes to get it. Also, @recharte wanted to discuss the UX of the CLI at the nearest triad weekly and I assume we will revisit the list command.
Right now, the list command returns only versions and database engines which IMO does not provide any value for the user in comparison to the UI.
Another point is that to fix it completely we need to add filtration by cluster name for the list kubernetes endpoint to provide the end user the ability to use cluster name as an identifier to list different resources
CHECKLIST
Jira
Tests