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
..
cmd.go	Only hide commands if the env variable is set.	2016-09-19 13:28:15 -04:00
create.go	Remove remaining registry methods from DockerCLI.	2016-09-09 15:50:01 -04:00
inspect.go	Fix typs from go to Go	2016-10-18 19:40:16 +08:00
inspect_test.go	Fix broken JSON support in cli/command/formatter	2016-10-17 08:07:17 +00:00
list.go	return nil when no node or service to avoid additional api call	2016-10-11 10:59:16 +08:00
opts.go	Service update failure thresholds and rollback	2016-10-18 10:09:50 -07:00
opts_test.go	Fix cli/command/service/opts_test.go, and add some extra test cases	2016-09-27 15:27:02 +00:00
ps.go	Move api/client -> cli/command	2016-09-08 15:46:29 -04:00
remove.go	Move api/client -> cli/command	2016-09-08 15:46:29 -04:00
scale.go	validate service parameter in client side to avoid api call	2016-09-26 17:18:02 +08:00
update.go	Add force option to service update	2016-10-21 17:43:27 -07:00
update_test.go	Move api/client -> cli/command	2016-09-08 15:46:29 -04:00