Sebastiaan van Stijn 76439457d2 Fix stack deploy re-deploying service after --force ...

When updating a service with the `--force` option, the `ForceUpdate`
property of the taskspec is incremented.

Stack deploy did not take this into account, and reset this
field to its default value (0), causing the service to be
re-deployed.

This patch copies the existing value before updating the service.

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>

2018-03-26 15:24:28 +02:00

..

kubernetes

Post migration fixes

2018-03-05 19:41:17 -05:00

loader

Automated migration

2018-03-05 19:41:17 -05:00

options

Add support for multiple composefile when deploying

2018-01-29 17:27:25 -08:00

swarm

Fix stack deploy re-deploying service after --force

2018-03-26 15:24:28 +02:00

testdata

Refactor stack command

2017-12-26 11:45:56 +01:00

client_test.go

Refactor stack command

2017-12-26 11:45:56 +01:00

cmd.go

Annotate "stack" commands to be "swarm" and "kubernetes"

2018-01-22 15:44:47 -08:00

deploy.go

Print Stack API version in version command

2018-02-26 01:16:49 +01:00

list_test.go

Convert assert.Check with

2018-03-06 15:43:53 -05:00

list.go

Print Stack API version in version command

2018-02-26 01:16:49 +01:00

ps_test.go

Convert assert.Check(t, is.Error()) to assert.Error

2018-03-06 16:00:28 -05:00

ps.go

Print Stack API version in version command

2018-02-26 01:16:49 +01:00

remove_test.go

Convert assert.Check(t, is.Error()) to assert.Error

2018-03-06 16:00:28 -05:00

remove.go

Print Stack API version in version command

2018-02-26 01:16:49 +01:00

services_test.go

Convert assert.Check with

2018-03-06 15:43:53 -05:00

services.go

Print Stack API version in version command

2018-02-26 01:16:49 +01:00