Repository navigation
Would be nice to have a docker stack deploy --dry-run option #53
Description
Because it's not always obvious what state an existing stack is in when a docker stack deploy command is issued, it would be useful to be able to see a plan of action before it's executed to prevent surprises.
I'm proposing --dry-run as the option name.
Reacted by Kevin Crawley, Guido García, Benjamin Boudreau, Brano Zarnovican, Riaan Jacobs, Víctor A. Rodríguez, Ben, Jesper Ek, Alexandro de Oliveira, dansailer and 24 more
Activity
hairyhenderson commentedon May 9, 2017
Looks like this was already proposed in moby/moby#32365 though I'm not sure where the issue should reside with all the repo-shuffling that's going on 😉
netflash commentedon Nov 22, 2017
Are there any chances to see this live ?
immerrr commentedon Apr 11, 2018
FTR, the issue in moby repository is closed in favour of this one.
00dav00 commentedon May 25, 2018
Any updates on this one? It would be a very useful option.
Merge pull request docker#53 from andrewhsu/sync-with-cli-18.09
bcsgh commentedon Nov 25, 2020
And now for the roughly annual update where someone says they would also find this useful. :-(
haraldfw commentedon Sep 21, 2021
I would also find this very helpful
Re4zOon commentedon Jan 11, 2022
Just to have the annual update: I would also find this helpful.
scripts/build: make sure osusergo is set for static with CGO enabled
scripts/build: make sure osusergo is set for static with CGO enabled
josteinaj commentedon Aug 31, 2023
I would also find this very helpful!
The important thing I want to know is which services will be updated. I don't need a detailed diff or anything.
frizzr commentedon Oct 12, 2024
I will add to the chorus that having a
--dry-runoption would be incredibly useful.Merge pull request docker#53 from seemethere/cherry_pick_33419