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 describe component should display actual resources created and not just their Devfile component names #6229

Open
1 task
valaparthvi opened this issue Oct 17, 2022 · 5 comments
Labels
area/describe-component Issues or PRs related to `odo describe component` kind/user-story An issue of user-story kind lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/Medium Nice to have issue. Getting it done before priority changes would be great.

Comments

@valaparthvi
Copy link
Contributor

valaparthvi commented Oct 17, 2022

/kind user-story

User Story

As a user I want to odo describe component to show the k8s resources that are managed by odo and not just the name of the Devfile component So that I know what the resource really is.

Acceptance Criteria

  • It should show k8s resource in the form of <devfile component name>: <Resource>/<Resource Name>
$ odo describe component
--- omitted for brevity ---

Container components:
 •  runtime : registry.access.redhat.com/ubi8/nodejs-14:latest

Kubernetes components:
 •  outerloop-deployment: Deployment/my-nodejs-app
 •  outerloop-service: Service/my-nodejs-app
 •  outerloop-url: Ingress/my-nodejs-app

Links

  • Related Epic (mandatory):

/kind user-story

Reproduction steps

  1. Use the Devfile defined in the advanced guide(https://odo.dev/docs/user-guides/advanced/deploy/nodejs/) to create a component.
  2. odo deploy to deploy it on the cluster.
  3. odo describe component and check the section on "Kubernetes Component"
@openshift-ci openshift-ci bot added the kind/bug Categorizes issue or PR as related to a bug. label Oct 17, 2022
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label Oct 17, 2022
@rm3l rm3l added this to odo Project Oct 17, 2022
@kadel
Copy link
Member

kadel commented Oct 18, 2022

I agree that the new suggested output is better, but this is not a bug.

It works as it was originally intended (#5661)

This is a feature request or feature enhancement.

It should be converted to a user story.
I'm adding needs-information label as a reminder that it needs to be converted to user-story

@kadel kadel added kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation triage/needs-information Indicates an issue needs more information in order to work on it. and removed kind/bug Categorizes issue or PR as related to a bug. labels Oct 18, 2022
@rm3l rm3l removed the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label Dec 12, 2022
@valaparthvi valaparthvi added kind/user-story An issue of user-story kind and removed kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation triage/needs-information Indicates an issue needs more information in order to work on it. labels Jun 22, 2023
@github-actions
Copy link
Contributor

A friendly reminder that this issue had no activity for 90 days. Stale issues will be closed after an additional 30 days of inactivity.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 21, 2023
@github-actions
Copy link
Contributor

This issue was closed because it has been inactive for 30 days since being marked as stale.

@github-actions github-actions bot added the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Oct 22, 2023
@github-project-automation github-project-automation bot moved this to Done ✅ in odo Project Oct 22, 2023
@rm3l
Copy link
Member

rm3l commented Oct 30, 2023

/remove-lifecycle rotten
/remove-lifecycle stale
/lifecycle frozen
/reopen

Still relevant.

@openshift-ci openshift-ci bot reopened this Oct 30, 2023
@openshift-ci
Copy link

openshift-ci bot commented Oct 30, 2023

@rm3l: Reopened this issue.

In response to this:

/remove-lifecycle rotten
/remove-lifecycle stale
/lifecycle frozen
/reopen

Still relevant.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci openshift-ci bot removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 30, 2023
@github-project-automation github-project-automation bot moved this from Done ✅ to To Do 📝 in odo Project Oct 30, 2023
@openshift-ci openshift-ci bot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Oct 30, 2023
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label Oct 30, 2023
@rm3l rm3l added area/describe-component Issues or PRs related to `odo describe component` and removed needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. labels Oct 30, 2023
@rm3l rm3l removed the status in odo Project Oct 30, 2023
@rm3l rm3l added the priority/Medium Nice to have issue. Getting it done before priority changes would be great. label Oct 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/describe-component Issues or PRs related to `odo describe component` kind/user-story An issue of user-story kind lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/Medium Nice to have issue. Getting it done before priority changes would be great.
Projects
Status: No status
Development

No branches or pull requests

3 participants