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

Provide component status in devworkspace-client #19151

Closed
benoitf opened this issue Feb 25, 2021 · 2 comments
Closed

Provide component status in devworkspace-client #19151

benoitf opened this issue Feb 25, 2021 · 2 comments
Labels
kind/enhancement A feature request - must adhere to the feature request template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P2 Has a minor but important impact to the usage or development of the system.

Comments

@benoitf
Copy link
Contributor

benoitf commented Feb 25, 2021

Is your enhancement related to a problem? Please describe.

Add component status (like endpoint URL merged into devfile components structure) + flag to know if component has been added by the tooling or if it was defined by user in its devfile (for example I have a component like 'java' with container including java/maven, etc ==> this is a user component, while che-theia if I didn't explicitely set an editor --> tooling component

Describe the solution you'd like

Provide status by grabbing information in devWorkspace routings, workspace pods and devWorkspace objects instead of letting clients pull information themselves and aggregate data on their own

Describe alternatives you've considered

Should be done until devfile/devworkspace-operator#261 is exposed

Additional context
@benoitf benoitf added kind/enhancement A feature request - must adhere to the feature request template. area/dev-workspace-client labels Feb 25, 2021
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Feb 25, 2021
@sleshchenko
Copy link
Member

I think devfile/devworkspace-operator#261 should be way to go, we just need to agree on the model for needed info

@Katka92 Katka92 added severity/P2 Has a minor but important impact to the usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Mar 1, 2021
@che-bot
Copy link
Contributor

che-bot commented Sep 2, 2021

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 2, 2021
@che-bot che-bot closed this as completed Sep 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/enhancement A feature request - must adhere to the feature request template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P2 Has a minor but important impact to the usage or development of the system.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@benoitf @sleshchenko @Katka92 @che-bot