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 catalog describe service" doesn't work outside a component directory #2487

Closed
dharmit opened this issue Dec 26, 2019 · 3 comments
Closed
Labels
estimated-size/M (10-20) Rough sizing for Epics. About 1 sprint of work for one person kind/bug Categorizes issue or PR as related to a bug. v2 Issue or PR that applies to the v2 of odo

Comments

@dharmit
Copy link
Member

dharmit commented Dec 26, 2019

/kind bug

What versions of software are you using?

Operating System: all

Output of odo version: master

How did you run odo exactly?

$ odo catalog describe service mysql-persistent
 ✗  The current directory does not represent an odo component. Use 'odo create' to create component here or switch to directory with a component

Actual behavior

odo didn't describe the service from outside a component directory

Expected behavior

odo should describe the service because we're just fetching the info from Service Catalog. We're not querying a service running in the cluster.

Any logs, error output, etc?

@openshift-ci-robot openshift-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Dec 26, 2019
@girishramnani
Copy link
Contributor

@dharmit I feel this should be area/catalog as the commands with odo catalog * come under that 🙂

@dharmit
Copy link
Member Author

dharmit commented Dec 26, 2019

Ack. But the description for area/service label says that anything related to service catalog could belong to it. Anyway, catalog seems more appropriate here. Thanks for the tip.

@kadel kadel added this to For concideration in Sprint 178 via automation Jan 6, 2020
@girishramnani girishramnani added state/Ready estimated-size/M (10-20) Rough sizing for Epics. About 1 sprint of work for one person labels Jan 6, 2020
@girishramnani
Copy link
Contributor

This is a duplicate of #2111. Hence closing this issue as its more recent.

Sprint 178 automation moved this from For concideration to Done Jan 7, 2020
@girishramnani girishramnani removed this from Done in Sprint 178 Jan 7, 2020
@rm3l rm3l added the v2 Issue or PR that applies to the v2 of odo label Jun 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
estimated-size/M (10-20) Rough sizing for Epics. About 1 sprint of work for one person kind/bug Categorizes issue or PR as related to a bug. v2 Issue or PR that applies to the v2 of odo
Projects
Archived in project
Development

No branches or pull requests

4 participants