96b0320d5c
This allows a plugin to be upgraded without requiring to
uninstall/reinstall a plugin.
Since plugin resources (e.g. volumes) are tied to a plugin ID, this is
important to ensure resources aren't lost.
The plugin must be disabled while upgrading (errors out if enabled).
This does not add any convenience flags for automatically
disabling/re-enabling the plugin during before/after upgrade.
Since an upgrade may change requested permissions, the user is required
to accept permissions just like `docker plugin install`.
Signed-off-by: Brian Goff <cpuguy83@gmail.com>
(cherry picked from commit
|
||
|---|---|---|
| .. | ||
| backend | ||
| blkiodev | ||
| container | ||
| events | ||
| filters | ||
| mount | ||
| network | ||
| reference | ||
| registry | ||
| strslice | ||
| swarm | ||
| time | ||
| versions | ||
| volume | ||
| auth.go | ||
| client.go | ||
| configs.go | ||
| error_response.go | ||
| id_response.go | ||
| image_summary.go | ||
| plugin.go | ||
| plugin_device.go | ||
| plugin_env.go | ||
| plugin_interface_type.go | ||
| plugin_mount.go | ||
| plugin_responses.go | ||
| port.go | ||
| seccomp.go | ||
| service_update_response.go | ||
| stats.go | ||
| types.go | ||
| volume.go | ||