Why no dry run ability?

Archives Ansible Project
1

You are about to be gasted back with your flabber!!! In fact, you
will soon have surplus flabber! And you will be back in the same
universe as everyone else!

--check mode (essentially dry run) is already in upstream for
file/copy, I'm working on diff output tonight, and we just have to
instrument a few other modules.

You must remember as you are running it, as with all configuration
management tools, though, that dry run is misleading and will never
tell you when something will fail or behave unexpectedly, and it will
always skip running commands.

Ansible does a lot of orchestration workflow other tools can simply
not do -- where the output of one command can affect another -- and as
such, dry run is just a simulation. Never forget that.

This is why we're calling it --check, and not dry run, and we'll warn
accordingly.

2

My gast has been been appropriately flabbered.

I don’t care what it’s called. Just as long as it’s there. Maybe I’m some super genius that understands these things better but the fact it’s a simulation and therefore not like the real thing where changes are actually made and therefore not necessarily 100% perfect simulation is obvious. It’s still a very important feature imho.