Allow --detach and --quiet flags when using --rollback

[thaJeztah]

Commit 78c204e (moby/moby@f9bd8ec / moby/moby#31108 in the moby repo) added a validation to prevent --rollback from being used in combination with other flags that update the service spec.

This validation was not taking into account that some flags only affect the CLI behavior, and are okay to be used when rolling back.

This patch updates the validation, and adds --quiet and --detach to the list of allowed flags.

relates to moby/moby#33444 (comment)

[aaronlehmann]

LGTM

[dnephin]

LGTM

[codecov-io]

Codecov Report

Merging #144 into master will not change coverage.
The diff coverage is 0%.

@@ Coverage Diff @@## master #144 +/- ##
=======================================
Coverage 44.96% 44.96% =======================================
Files 169 169 Lines 11378 11378 =======================================
Hits 5116 5116 Misses 5970 5970 Partials 292 292

[cpuguy83]

Kind of stinks we can't specify the rollback order when rolling back.

[aaronlehmann]

@cpuguy83: For the swarm manager to know it's doing a rollback, the rollback has to happen server-side instead of the client just submitting PreviousSpec as the new spec. But if the spec is being rolled back on the server side, there is no mechanism to tell the swarm manager "use the previous spec, except change X and Y and Z".

[thaJeztah]

Also related to this; #142

For the swarm manager to know it's doing a rollback, the rollback has to happen server-side instead of the client just submitting PreviousSpec as the new spec.

Perhaps a PATCH request could be used to allow updating the spec while rolling back (i.e., just allow setting some options)? Anyway, that's a different discussion 😄

[vdemeester]

LGTM 🐸