Branching Inconsistencies via Supabase CLI

🌲branching

CLI

Hi all!

First time poster, I've been trying to get preview deployments going, and I had some questions about the current branching behaviour. I am on the latest CLI version (2.72.8). If these questions are better asked elsewhere (via GitHub Issue or feature requests), let me know.

--with-data does not add new secret keys
I understand we are being encouraged to use the new secret keys. However, I noticed that when I branch on the supabase CLI with the --with-data flag set (e.g.

supabase branches create test-branch --with-data

supabase branches create test-branch --with-data

), the branch created doesn't give any secret keys, nor does it generate any. It only has the

service_role_key

service_role_key

Is there a reason why this is the case? Not using

--with-data

--with-data

does provide secret keys. I can see that the project is being restored when the with-data option is on, so perhaps this has something to do with it?

Branching Does not Provide Direct Connection Over Shared Pooler
When you create a new branch, in the "connect" option, it says something like:

# Connect to Supabase via Shared Connection Pooler
DATABASE_URL="postgresql://postgres.<redacted>:[YOUR-PASSWORD]@aws-1-us-east-2.pooler.supabase.com:6543/postgres?pgbouncer=true"

# Direct connection to the database through Shared Pooler (supports IPv4/IPv6). Used for migrations.
DIRECT_URL="postgresql://postgres.<redacted>:[YOUR-PASSWORD]@aws-1-us-east-2.pooler.supabase.com:5432/postgres"

# If your network supports IPv6 or you purchased IPv4 addon, use dedicated pooler
# DATABASE_URL="postgres://postgres:[YOUR-PASSWORD]@db.<redacted>.supabase.co:6543/postgres?pgbouncer=true"
# DIRECT_URL="postgres://postgres:[YOUR-PASSWORD]@db.<redacted>.supabase.co:5432/postgres"

# Connect to Supabase via Shared Connection Pooler
DATABASE_URL="postgresql://postgres.<redacted>:[YOUR-PASSWORD]@aws-1-us-east-2.pooler.supabase.com:6543/postgres?pgbouncer=true"

# Direct connection to the database through Shared Pooler (supports IPv4/IPv6). Used for migrations.
DIRECT_URL="postgresql://postgres.<redacted>:[YOUR-PASSWORD]@aws-1-us-east-2.pooler.supabase.com:5432/postgres"

# If your network supports IPv6 or you purchased IPv4 addon, use dedicated pooler
# DATABASE_URL="postgres://postgres:[YOUR-PASSWORD]@db.<redacted>.supabase.co:6543/postgres?pgbouncer=true"
# DIRECT_URL="postgres://postgres:[YOUR-PASSWORD]@db.<redacted>.supabase.co:5432/postgres"

But when you create a new branch, it only outputs the first and the very last URL. I was previously using the Shared Pooler option, and had to manually construct the URL.

Any insight (or pointing me elsewhere as necessary) would be greatly appreciated. Thanks in advance!

Branching Inconsistencies via Supabase CLI

🌲branching

CLI

supabase branches create test-branch --with-data

supabase branches create test-branch --with-data

), the branch created doesn't give any secret keys, nor does it generate any. It only has the

service_role_key

service_role_key

Is there a reason why this is the case? Not using

--with-data

--with-data

# Connect to Supabase via Shared Connection Pooler
DATABASE_URL="postgresql://postgres.<redacted>:[YOUR-PASSWORD]@aws-1-us-east-2.pooler.supabase.com:6543/postgres?pgbouncer=true"

# Direct connection to the database through Shared Pooler (supports IPv4/IPv6). Used for migrations.
DIRECT_URL="postgresql://postgres.<redacted>:[YOUR-PASSWORD]@aws-1-us-east-2.pooler.supabase.com:5432/postgres"

# If your network supports IPv6 or you purchased IPv4 addon, use dedicated pooler
# DATABASE_URL="postgres://postgres:[YOUR-PASSWORD]@db.<redacted>.supabase.co:6543/postgres?pgbouncer=true"
# DIRECT_URL="postgres://postgres:[YOUR-PASSWORD]@db.<redacted>.supabase.co:5432/postgres"

# Connect to Supabase via Shared Connection Pooler
DATABASE_URL="postgresql://postgres.<redacted>:[YOUR-PASSWORD]@aws-1-us-east-2.pooler.supabase.com:6543/postgres?pgbouncer=true"

# Direct connection to the database through Shared Pooler (supports IPv4/IPv6). Used for migrations.
DIRECT_URL="postgresql://postgres.<redacted>:[YOUR-PASSWORD]@aws-1-us-east-2.pooler.supabase.com:5432/postgres"

# If your network supports IPv6 or you purchased IPv4 addon, use dedicated pooler
# DATABASE_URL="postgres://postgres:[YOUR-PASSWORD]@db.<redacted>.supabase.co:6543/postgres?pgbouncer=true"
# DIRECT_URL="postgres://postgres:[YOUR-PASSWORD]@db.<redacted>.supabase.co:5432/postgres"

Branching Inconsistencies via Supabase CLI

Branching Inconsistencies via Supabase CLI

Similar Threads

Similar Threads

Similar Threads