f37117045c
This patch introduces a new experimental engine-level plugin management with a new API and command line. Plugins can be distributed via a Docker registry, and their lifecycle is managed by the engine. This makes plugins a first-class construct. For more background, have a look at issue #20363. Documentation is in a separate commit. If you want to understand how the new plugin system works, you can start by reading the documentation. Note: backwards compatibility with existing plugins is maintained, albeit they won't benefit from the advantages of the new system. Signed-off-by: Tibor Vass <tibor@docker.com> Signed-off-by: Anusha Ragunathan <anusha@docker.com>
13 lines
339 B
Go
13 lines
339 B
Go
// +build experimental
|
|
|
|
package main
|
|
|
|
import (
|
|
"github.com/docker/docker/api/server/router"
|
|
pluginrouter "github.com/docker/docker/api/server/router/plugin"
|
|
"github.com/docker/docker/plugin"
|
|
)
|
|
|
|
func addExperimentalRouters(routers []router.Router) []router.Router {
|
|
return append(routers, pluginrouter.NewRouter(plugin.GetManager()))
|
|
}
|