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 use machine API for machine handling #1929

Closed
garagatyi opened this issue Jul 25, 2016 · 0 comments
Closed

Do not use machine API for machine handling #1929

garagatyi opened this issue Jul 25, 2016 · 0 comments
Assignees
@RomanNikitenko
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed.
Milestone
5.0.0-M5

Comments

@garagatyi
Copy link

To introduce Environment SPI and separate environment handling logic into implementation-specific component we need to stop using Machine API for handling machines.
Now next calls are used from IDE only:

  • get machine by ID
  • get all machines of workspace
  • destroy machine
    UD doesn't use machine API, so don't need changes.
@garagatyi garagatyi mentioned this issue Jul 25, 2016
Closed
4 tasks
@vparfonov vparfonov added kind/task Internal things, technical debt, and to-do tasks to be performed. sprint/next team/ide labels Jul 26, 2016
@RomanNikitenko RomanNikitenko added the status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. label Aug 5, 2016
@RomanNikitenko RomanNikitenko added status/in-progress This issue has been taken by an engineer and is under active development. and removed status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. labels Aug 16, 2016
@RomanNikitenko RomanNikitenko added status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. and removed status/in-progress This issue has been taken by an engineer and is under active development. labels Sep 5, 2016
@vkuznyetsov vkuznyetsov mentioned this issue Sep 6, 2016
Closed
3 tasks
@RomanNikitenko RomanNikitenko added status/in-progress This issue has been taken by an engineer and is under active development. and removed status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. labels Sep 9, 2016
@RomanNikitenko RomanNikitenko mentioned this issue Sep 16, 2016
Merged
2 tasks
@RomanNikitenko RomanNikitenko added status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. and removed status/in-progress This issue has been taken by an engineer and is under active development. labels Sep 16, 2016
@RomanNikitenko RomanNikitenko added this to the 5.0.0-M5 milestone Sep 29, 2016
@RomanNikitenko RomanNikitenko removed the status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. label Sep 29, 2016
@bmicklea bmicklea mentioned this issue Oct 8, 2016
Closed
56 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@RomanNikitenko RomanNikitenko

Labels
kind/task Internal things, technical debt, and to-do tasks to be performed.
Projects
None yet
Milestone
5.0.0-M5
Development

No branches or pull requests
3 participants
@vparfonov @garagatyi @RomanNikitenko