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.

Sign up for GitHub

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

Jump to bottom

odo describe component without Devfile: display remote source code location for each container component #6498

Closed
Tracked by #6453
rm3l opened this issue Jan 17, 2023 · 3 comments
Closed
Tracked by #6453

odo describe component without Devfile: display remote source code location for each container component #6498

rm3l opened this issue Jan 17, 2023 · 3 comments
Labels
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. needs-triage Indicates an issue or PR lacks a `triage/*` and requires one.

Comments

@rm3l
Copy link
Member

rm3l commented Jan 17, 2023 •
edited
Loading

When executed using the --name flag, it should get the information from the PROJECT_SOURCE (or PROJECTS_ROOT ?) environment variable from the running container spec
@rm3l rm3l mentioned this issue Jan 17, 2023
Closed
6 tasks
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label Jan 17, 2023
@rm3l rm3l added this to odo Project Jan 17, 2023
@rm3l
Copy link
Member Author

rm3l commented Jan 17, 2023 •
edited
Loading

NOTES (Cabal 2023-01-17):

@rm3l rm3l changed the title When executed using the --name flag, it should get the information from the PROJECT_SOURCE (or PROJECTS_ROOT ?) environment variable from the running container spec odo describe component without Devfile: display remote source code location for each container component Jan 17, 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 Jun 11, 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 Jul 12, 2023
@github-project-automation github-project-automation bot moved this to Done ✅ in odo Project Jul 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
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. needs-triage Indicates an issue or PR lacks a `triage/*` and requires one.
Projects
odo Project
Archived in project
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rm3l