Require meaningful confirmation before remote database reset

[trooney]

Hello there!

I enjoy using Supabase. The functionality available by the CLI is great. Today I wanted to reset the remote database. Sure enough that was built right into the CLI 🎸

While convenient, I wonder if dropping a database with just y as confirmation is too easy. 😟

$ supabase db reset --linked

Using workdir /abc123
Do you want to reset the remote database? [y/N] y
Resetting remote database...
Seeding data from supabase/seed.sql...

Maybe a more explicit confirmation step could be added?

[silentworks]

Most services only give you one confirmation when deleting an account unless they are trying to upsell you something, I don't think this is much different. You are explicitly asked if you wish to reset the remote db, plus the first confirmation I would say is you even typing the --linked as this isn't a default flag when you do db reset. This is my 2 cents on this.

[trooney]

That's a fair point. And I'll acknowledge explicitness is a subjective thing 😆

Some services implement a confirmation step that requires we name the resource.

Here's an example from AWS SES:

The additional flag (--linked) indicates the operation you want to perform. Requiring some kind of specific user input would be an additional and more explicit guard against a destructive operation. Some might feel databases might warrant such safeguards.

[silentworks]

You are comparing a web portal where you click a button compared to something you are explicitly typing. You explicitly type --linked and then you explicitly type y again after being asked to confirm. So you confirmed twice, but you are asking for yet again another confirmation which to me is an overkill and not really worth the effort.