Aaron Lehmann 57ae29aa74 Add failure action for rolling updates ... This changes the default behavior so that rolling updates will not proceed once an updated task fails to start, or stops running during the update. Users can use docker service inspect --pretty servicename to see the update status, and if it pauses due to a failure, it will explain that the update is paused, and show the task ID that caused it to pause. It also shows the time since the update started. A new --update-on-failure=(pause|continue) flag selects the behavior. Pause means the update stops once a task fails, continue means the old behavior of continuing the update anyway. In the future this will be extended with additional behaviors like automatic rollback, and flags controlling parameters like how many tasks need to fail for the update to stop proceeding. This is a minimal solution for 1.12. Signed-off-by: Aaron Lehmann <aaron.lehmann@docker.com>		2016-07-25 08:51:19 -07:00
..
cmd.go	Add experimental docker stack commands	2016-06-14 14:56:35 -04:00
create.go	Change the add/update flags to include 'add'	2016-07-13 16:06:25 -04:00
inspect.go	Add failure action for rolling updates	2016-07-25 08:51:19 -07:00
list.go	Merge pull request #24266 from allencloud/add_cmd_docker_stack_services_STACKNAME	2016-07-20 18:38:08 +02:00
opts.go	Add failure action for rolling updates	2016-07-25 08:51:19 -07:00
opts_test.go	api/client/service: mount option defaults and aliases	2016-07-21 17:31:33 -07:00
remove.go	Fix the usage for service rm command	2016-07-20 18:27:26 +09:00
scale.go	re-vendor engine-api	2016-07-06 21:14:14 -04:00
tasks.go	Remove shorthand flags for "mount", "pretty", and "no-resolve"	2016-07-13 18:47:29 +02:00
update.go	Add failure action for rolling updates	2016-07-25 08:51:19 -07:00
update_test.go	Change mount-types to lowercase	2016-07-21 11:25:42 +02:00