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

server:start doesn't work if Che has already been deployed #77

Closed
l0rd opened this issue Apr 1, 2019 · 4 comments
Closed

server:start doesn't work if Che has already been deployed #77

l0rd opened this issue Apr 1, 2019 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@l0rd
Copy link
Collaborator

l0rd commented Apr 1, 2019

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.

@l0rd
Copy link
Collaborator Author

l0rd commented Aug 19, 2019

@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 l0rd removed their assignment Aug 19, 2019
@sleshchenko
Copy link
Contributor

@l0rd I've already made some changes as well. Thanks for sharing your changes, will take a look and probably reuse some parts.

@sleshchenko
Copy link
Contributor

The work is suspended in the flavor of eclipse-che/che-operator#71

@benoitf
Copy link
Collaborator

benoitf commented Sep 9, 2019

Kamino closed and cloned this issue to eclipse/che

@benoitf benoitf closed this as completed Sep 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants