moby/plugin/interface.go

package plugin

import "github.com/docker/docker/pkg/plugins"

// Plugin represents a plugin. It is used to abstract from an older plugin architecture (in pkg/plugins).
type Plugin interface {
	Client() *plugins.Client
	Name() string
	IsLegacy() bool
}
plugins: experimental support for new plugin management 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> 2016-05-16 15:50:55 +00:00			`package plugin`

			`import "github.com/docker/docker/pkg/plugins"`

			`// Plugin represents a plugin. It is used to abstract from an older plugin architecture (in pkg/plugins).`
			`type Plugin interface {`
			`Client() *plugins.Client`
			`Name() string`
Add only legacy plugins to the legacy lookup map. Legacy plugin model maintained a map of plugins. This is not used by the new model. Using this map in the new model causes incorrect lookup of plugins. This change uses adds a plugin to the map only if its legacy. Signed-off-by: Anusha Ragunathan <anusha@docker.com> (cherry picked from commit 8fd779dc28a11d8727d76e9553379b0c854f7c4c) Signed-off-by: Tibor Vass <tibor@docker.com> 2016-07-18 22:39:27 +00:00			`IsLegacy() bool`
plugins: experimental support for new plugin management 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> 2016-05-16 15:50:55 +00:00			`}`