-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
CHE-1849: Modify start workspace by ID API method #1907
Conversation
@evoevodin @skabashnyuk Please take a look |
@@ -116,10 +116,14 @@ | |||
* workspace ID | |||
* @param envName | |||
* the name of the workspace environment that should be used for start | |||
* @param isRecover |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What about option when server decides recover or not depending on auto-restore behavior?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a client method and it will always send request with defined restore
parameter, so server will never use auto-restore behavior if this method called
Please add yourself as author to the classes you changed |
Build # 1284 - FAILED Please check console output at http://ci.codenvy-dev.com/jenkins/job/che-pullrequests-build/1284/ to view the results. |
1272910
to
f304e10
Compare
Added myself to authors |
} | ||
}); | ||
} | ||
|
||
private void startById(@NotNull String workspaceId, | ||
@Nullable String envName, | ||
@Nullable boolean restore, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How primitive can be null?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I mean that Nullable annotations looks useless.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this have to be fixed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
LGTM |
+1 |
Build # 1291 - FAILED Please check console output at http://ci.codenvy-dev.com/jenkins/job/che-pullrequests-build/1291/ to view the results. |
Build # 1294 - FAILED Please check console output at http://ci.codenvy-dev.com/jenkins/job/che-pullrequests-build/1294/ to view the results. |
ок |
b655b54
to
462c071
Compare
When user starts workspace that has snapshot the 'recover from snapshots?' dialog will be shown. If user will select not to recover and auto-restore will be enabled workspace will be recovered from snapshot anywhere.
Build # 1302 - FAILED Please check console output at http://ci.codenvy-dev.com/jenkins/job/che-pullrequests-build/1302/ to view the results. |
What does this PR do?
Adds query parameter to
startById()
method inWorkspaceService
to know if workspace needs to be recovered from snapshot or just to start.
Removes
recoverWorkspace()
API method fromWorkspaceService
.What issues does this PR fix or reference?
When user starts workspace that has snapshot the 'recover from snapshots?' dialog will be shown.
If user will select not to recover and auto-restore will be enabled workspace will be recovered from snapshot anywhere.
#1849
Tests written?
Yes
Docs requirements?
API changes