Is it possible to get better security for special DistSQL?

[sandynz]

Hi,

I found there is a special DistSQL: RESET SCALING {jobId}, what it doing is to truncate all tables of target data sources configured in scaling job configuration.

It's dangerous to use, especially on production environment. Is there possible way to mke it more secure for end users? e.g.

1. show a confirmation, end user input yes or no to accept or cancel to do it
2. show a confirmation, end user input input password to do it
3. support rename dangerous command, just like Redis Disabling of specific commands
4. Add a global switch to control whether it's permitted or not, example configuration: flushdb-permitted: false

Option 4 should be easier to implement.

If it could not be supported, I prefer to remove RESET SCALING {jobId}.

How do you think, any feedback is welcome.