-
Notifications
You must be signed in to change notification settings - Fork 65
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
server:start doesn't work if Che has already been deployed #77
Comments
@sleshchenko I am perfectly fine if you are work on this issue but I started working on it a few months ago: l0rd@6682c5c. I wasn't happy with that preliminary work (too complicated) and never actually created a PR. Unassigning it to myself. |
@l0rd I've already made some changes as well. Thanks for sharing your changes, will take a look and probably reuse some parts. |
The work is suspended in the flavor of eclipse-che/che-operator#71 |
Kamino closed and cloned this issue to eclipse/che |
If Che is already deployed the flow should be different:
a) if Che is deployed and running: returns saying that Che is already running
b) if Che is deployed and stopped: starts Che and return saying that Che was already deployed
There is also #32 that is about these 2 flows but extending them using the flag
--if-already-exist
flag.The text was updated successfully, but these errors were encountered: