Aaron Lehmann c9fdf9abf8 Add force option to service update ... Currently, there's no way to restart the tasks of a service without making an actual change to the service. This leads to us giving awkward workarounds as in https://github.com/docker/docker.github.io/pull/178/files, where we tell people to scale a service up and down to restore balance, or make unnecessary changes to trigger a restart. This change adds a --force option to "docker service update", which forces the service to be updated even if no changes require that. Since rolling update parameters are respected, the user can use "docker service --force" to do a rolling restart. For example, the following is supported: docker service update --force --update-parallelism 2 \ --update-delay 5s myservice Since the default value of --update-parallelism is 1, the default behavior is to restart the service one task at a time. Signed-off-by: Aaron Lehmann <aaron.lehmann@docker.com>		2016-10-21 17:43:27 -07:00
..
container.go	Add engine-api types to docker	2016-09-07 11:05:58 -07:00
network.go	Add support for docker run in swarm mode overlay	2016-09-07 21:20:41 -07:00
node.go	Add engine-api types to docker	2016-09-07 11:05:58 -07:00
service.go	Add force option to service update	2016-10-21 17:43:27 -07:00
swarm.go	Let swarmkit handle cluster defaults in swarm init if not specified	2016-09-27 04:19:38 -07:00
task.go	Fix partial/full filter issue in service tasks --filter	2016-09-26 16:01:20 -07:00