848e510213
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> Upstream-commit: f37117045c5398fd3dca8016ea8ca0cb47e7312b Component: engine
22 lines
577 B
Go
22 lines
577 B
Go
// +build experimental
|
|
|
|
package plugin
|
|
|
|
import (
|
|
"net/http"
|
|
|
|
enginetypes "github.com/docker/engine-api/types"
|
|
)
|
|
|
|
// Backend for Plugin
|
|
type Backend interface {
|
|
Disable(name string) error
|
|
Enable(name string) error
|
|
List() ([]enginetypes.Plugin, error)
|
|
Inspect(name string) (enginetypes.Plugin, error)
|
|
Remove(name string) error
|
|
Set(name string, args []string) error
|
|
Pull(name string, metaHeaders http.Header, authConfig *enginetypes.AuthConfig) (enginetypes.PluginPrivileges, error)
|
|
Push(name string, metaHeaders http.Header, authConfig *enginetypes.AuthConfig) error
|
|
}
|