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

CHE-750 Remove snapshots on workspace removal #1015

Merged
merged 1 commit into from
Apr 12, 2016
Merged

CHE-750 Remove snapshots on workspace removal #1015

merged 1 commit into from
Apr 12, 2016

Conversation

mkuznyetsov
Copy link
Contributor

@evoevodin @garagatyi review please

@garagatyi
Copy link

LGTM

@skabashnyuk
Copy link
Contributor

ok

@@ -279,6 +279,9 @@ public void delete(@ApiParam("The workspace id") @PathParam("id") String id) thr
ConflictException,
ForbiddenException {
ensureUserIsWorkspaceOwner(id);
if (!workspaceManager.getSnapshot(id).isEmpty()) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I understand that it is out scope of current issue. But maybe it would be better to rename getSnapshot to getSnapshots?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think no, the main idea of this method name is get workspace snapshot which is actually the list of machine snapshots, we also planed to create separate object describing workspace snapshot, that's why this name fits our needs

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 Thanks for explanation

@mkuznyetsov mkuznyetsov merged commit dcf4cf7 into master Apr 12, 2016
@mkuznyetsov mkuznyetsov deleted the CHE-750 branch April 22, 2016 13:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants