I'd kind of rather have an internal-only command that does this instead exposing it to the user. For two reasons.

1. The option is not Heroku compliant
2. Avoids more arg parsing code

Thats fine with me, something in common? That way plugins could still use it, but not users.

My concern is that adding something like this to common exposes configuration management outside of the config plugin, which I don't think is so great.

How about dokku config:nset or something similar that wraps config:set but bypasses the restart?

Well it wouldn't be able to wrap config:set but would be wrapped. We can omit it from the help output so and document it in the development guide for plugins :)

Works for me.

ping @josegonzalez

Merge once this passes :) Good work!