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

Do not allow workspace start with workspace config #13517

Closed
2 tasks done
skabashnyuk opened this issue Jun 12, 2019 · 4 comments
Closed
2 tasks done

Do not allow workspace start with workspace config #13517

skabashnyuk opened this issue Jun 12, 2019 · 4 comments
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P1 Has a major impact to usage or development of the system.
Milestone
7.19

Comments

@skabashnyuk
Copy link
Contributor

skabashnyuk commented Jun 12, 2019 •
edited
Loading

Description

Since we are moving forward in devfile-based workspaces it would be logical to turn off the ability to start workspace configured with help of wsconfig. We can do that after
@skabashnyuk skabashnyuk added kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system. team/platform labels Jun 12, 2019
@Ohrimenko1988 Ohrimenko1988 mentioned this issue Jun 12, 2019
Closed
@skabashnyuk skabashnyuk mentioned this issue Jun 14, 2019
Closed
@dneary
Copy link
Contributor

dneary commented Jun 14, 2019

This task also depends on providing documentation for people with existing workspace configs on how to create an equivalent Devfile.

@skabashnyuk skabashnyuk added this to the Backlog - Platform milestone Oct 10, 2019
@che-bot
Copy link
Contributor

che-bot commented Apr 8, 2020

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 Apr 8, 2020
@skabashnyuk
Copy link
Contributor Author

/remove-lifecycle stale

@skabashnyuk skabashnyuk removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 8, 2020
@che-bot
Copy link
Contributor

che-bot commented Oct 28, 2020

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 Oct 28, 2020
@skabashnyuk skabashnyuk modified the milestones: Backlog - Platform, 7.19 Oct 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Milestone
7.19
Development

No branches or pull requests
3 participants
@dneary @skabashnyuk @che-bot