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
..
convert	Add force option to service update	2016-10-21 17:43:27 -07:00
executor	Update docker stop and docker restart to allow not specifying timeout and use the one specified at container creation time.	2016-10-17 12:53:35 -07:00
provider	Add engine-api types to docker	2016-09-07 11:05:58 -07:00
cluster.go	Vendor swarmkit in master	2016-10-20 13:49:22 -07:00
filters.go	Add engine-api types to docker	2016-09-07 11:05:58 -07:00
helpers.go	Fix spelling in comments, strings and documentation	2016-07-03 20:58:11 +03:00
listen_addr.go	Add fallback to resolveSystemAddr() in linux	2016-09-09 13:27:57 -07:00
listen_addr_linux.go	Add fallback to resolveSystemAddr() in linux	2016-09-09 13:27:57 -07:00
listen_addr_others.go	Add fallback to resolveSystemAddr() in linux	2016-09-09 13:27:57 -07:00