Skip to content

fix(e2e): move roles.sql out of supabase/ so the CLI stops seeding it - #1

Open
amal66 wants to merge 1 commit into
thijsdezoete:mainfrom
Open-Legal-Products:fix/196-e2e-supabase-roles
Open

fix(e2e): move roles.sql out of supabase/ so the CLI stops seeding it#1
amal66 wants to merge 1 commit into
thijsdezoete:mainfrom
Open-Legal-Products:fix/196-e2e-supabase-roles

Conversation

@amal66

@amal66 amal66 commented Jul 31, 2026

Copy link
Copy Markdown

Fixes the e2e (playwright) failure on Open-Legal-Products#196.

Why e2e fails: the Supabase CLI auto-seeds supabase/roles.sql as globals during supabase start. On the current supabase/postgres 17.x images that seed connection is not a superuser, and supabase_auth_admin is a reserved role, so the ALTER ROLE fails with SQLSTATE 42501 and the job dies before Playwright ever runs.

Fix: the file only exists for the docker-compose stack, where it runs as the init superuser via /docker-entrypoint-initdb.d. Move it to docker/db-init/ and update the compose mount, so CI's supabase start no longer picks it up. Compose behavior is unchanged.

🤖 Generated with Claude Code

The Supabase CLI auto-seeds supabase/roles.sql as globals during
'supabase start'. On the current supabase/postgres 17.x images that
seed connection is not a superuser, and supabase_auth_admin is a
reserved role, so ALTER ROLE fails with SQLSTATE 42501 and kills the
e2e job before Playwright runs.

The file only exists for the docker-compose stack, where it runs as
the init superuser via /docker-entrypoint-initdb.d. Move it to
docker/db-init/ and update the compose mount; CI's 'supabase start'
no longer sees it.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant