Plugin manager as separate service

Registered by Evgeniy L on 2015-02-26

Currently we have thousands of line of code in fuelclient to install/delete/update/downgrade/register/unregister the plugins.
By design fuel client is a wrong place to keep this logic and this logic should be placed in separate Plugin Manager service which should be installed in separate container.

Blueprint information

Status:
Not started
Approver:
Dmitry Pyzhov
Priority:
High
Drafter:
Evgeniy L
Direction:
Needs approval
Assignee:
Vladimir Sharshov
Definition:
New
Series goal:
Accepted for 7.0.x
Implementation:
Not started
Milestone target:
milestone icon 7.0

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.