Closed WhoAteDaCake closed 2 months ago
I'm unable to reproduce this locally. Are you sure POSTGRES_PASSWORD
is not an empty value?
Another alternative is to set the SUPABASE_DB_PASSWORD
env var.
@sweatybridge I've tried SUPABASE_DB_PASSWORD
too, all of them fail with
failed to connect to postgres: failed to connect to `host=aws-0-eu-west-2.pooler.supabase.com user=postgres.sjxjsdkdpuwueblulnqs database=postgres`: failed SASL auth (invalid SCRAM server-final-message received from server)
The only thing that works is putting in the password through the prompt
Update: changed my password to no special characters one and now it works. Previous one was 8b@$P8^oNZJap2
Describe the bug Should be able to use
supabase link
with args or env variables, so it can be used in github actiomsTo Reproduce Steps to reproduce the behavior:
supabase link --project-ref "Ref" --password "Password here"
Expected behavior
Screenshots
System information Rerun the failing command with
--create-ticket
flag.Versions of services: [output from
supabase services
command]