unify password entry across CLI commands

[Thorsten-Kd]

Describe the bug
I am using several CLI commands that support different ways of inputing the password. For example:

• db link and db push support the -p parameter to specify the password
• storage rm only supports stdin and in automation scripts I can work around it by piping echo $password before the command
• db reset supports only the secure way of stdin and I need to use expect and some workarounds to be able to input the password in an automation script. Additionally this solution requires to specify the exact prompt from the CLI that needs to be answered, e.g. "Enter your database password:". If the prompt changes the script won't work anymore.

To Reproduce
Steps to reproduce the behavior:

1. Try echo $password | db reset ... which won't work
2. Try -p $password parameter in storage or db reset commands

Expected behavior
-p parameter is supported in all CLI apis that require a password

System information

• Version of CLI: [e.g. v2.33.7]

[sweatybridge]

The latest CLI release no longer requires db password for any commands. All database access will default to using a temporary role created from your personal access token. Could you give that a try?

npx supabase@latest db push

We will probably deprecate the -p flag in the long run but continue to maintain the SUPABASE_DB_PASSWORD env var for local and CI runners.

[Thorsten-Kd]

Thanks @sweatybridge That solved it. I am now using the SUPABASE_DB_PASSWORD, wasn't aware of it before. Makes it way easier.