dry-run

It sure would be nice to have `--dry-run --verbose` to see exactly what it's going to do.

And yet the concept of the invocation `fuck --dry-run` is surely unappealing.

However, `--dry-run` would still get me 95% the way to where I'd need to be to use CF in production.

While there is a little overhead in learning something like ansible, being able to provision another machine to do a dry-run more than makes up for that cost.

I'm surprised that the CloudFormation team hasn't added a --dry-run option yet.

And it generally cost prohibitive to do a full dry-run with only a cargo full of, say, bricks, because a single launch costs well north of a hundred million dollars.

I think the ability to do a dry-run upload without prepaying (which Colin has already said is on the way) will be pretty much a complete solution.

`--dry-run` tells you what it would do at a point-in-time, but isn't a guarantee that by the time you update a stack that that is what would actually happen.

You can use tarsnap's --dry-run option (along with --print-stats) to find out how much space your data will take up; unfortunately you need to have a key file before you can run that, and you can't create a key file until you've created a tarsnap account and added money to it.

You're right to some extent, but I think many of these 'knobs' have a good reason to exist (--dry-run, -a, -z for rsync for instance) and cannot be usefully, or at all, replaced by more composability.

Well it seems Important but disrespectful, as the audience never even turned up, yet I was still made to ‘dry-run’ the whole meeting from start to finish for an hour and a half as if there was full attendance and interest in what I was saying.

(To me, burn out is a result of feeling like you're not getting anywhere, and that just plain isn't the case at a company where we consistently ship things with huge scopes, on time and to resounding success.) Yeah, there's exec demos, and yeah there's dry-run meetings for them, but you know what?

It seems to me that you're looking for excuses, as if this concept of 'dry-run' meetings only happens to be within the author's "hundred-person bubble".

I wonder if there's room for adding a "--dry-run-yes-really-dont-run-any-recipes-at-all" flag to make.

In S&N, Silver discusses how the ratings agencies gave their ratings software to the banks, so the banks could "dry-run" their tranches to get the best ratings available.

Or maybe a more general solution, instead of "--dry-run-yes-really", would be providing access to make's parser as a library, instead of having to parse the output of "make -p".