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

"odo service list" should output Operator backed service as "<servicekind>/<servicename>" #3560

Closed
dharmit opened this issue Jul 14, 2020 · 1 comment · Fixed by #3561
Closed
Labels
kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation

Comments

@dharmit
Copy link
Member

dharmit commented Jul 14, 2020

/kind feature
/kind discussion
/area UX

Currently, we're listing services backed by Operators as below:

$ odo service list
NAME        TYPE            AGE
example     Cockroachdb     3s
example     EtcdCluster     3m22s

As proposed in #3557, if a user wants to connect to EtcdCluster named example, they need to do odo link EtcdCluster/example. For better UX, it would be helpful if we list the services as below instead:

$ odo service list
NAME                          AGE
Cockroachdb/example           3s
EtcdCluster/example           3m22s
EtcdCluster/myawesomeetcd     3s

Originally posted by @dharmit in #2920 (comment)

@openshift-ci-robot openshift-ci-robot added kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation kind/discussion labels Jul 14, 2020
@dharmit
Copy link
Member Author

dharmit commented Jul 14, 2020

I have opened a PR based on the discussion had in #2920. Completely open to suggestions/discussion if we would like to have different output format.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants