[aqme28]

I've done that, but I hate the term "wet run."

I use "live run" now, which I think gets the point across without being sort of uncomfortable.

[IgorPartola]

--with-danger

--make-it-so

--do-the-thing

--go-nuts

--safety-off

So many fun options.

[Darfk]

I'm a fan of --safety-off. It gives off a 'aim away from face' or 'mishandle me and I'll blow a chunk out of your DB' vibe.

[tetha]

I find it important to include system information in here as well, so just copy-pasting an invocation from system A to system B does not run.

For example, our database restore script has a parameter `--yes-delete-all-data-in` and it needs to be parametrized with the PostgreSQL cluster name. So a command with `--yes-delete-all-data-in=pg-accounting` works on exactly one system and not on other systems.

[torstenvl]

It's in the UI not the command line, but I like Chromium's thisisunsafe

[JsonCameron]

I've done a few --execute --i-know-what-im-doing for some more dangerous scripts

[altairprime]

--commit is solid too

[bregma]

    --moisten

[Quekid5]

Moist run is the way.