bug: Supabase integration does not work with custom domains

Question

kylewill opened this issue 2 months ago · comments

Problem: If a user has a custom domain and adds that to their environment variables Trigger.dev is not able to use the Supabase Management API.

The issue seems to be trigger is using the URL from the config (expecting {project-id}.supabase.co format).

But if it's a custom domain trigger extracts the subdomain and uses that as the project id.

Reproduction

Add a custom domain in a supabase project

Add the custom domain to the .env

Note how triggers are not created and received a 403 error.

Workaround

The user must use the {project-id}.supabase.co format in their environment.

I do not know if there are other issues with doing this yet but suspect so.

Suggested fix

If the supabase url is not in the {project-id}.supabase.co format, do an nslookup to see where it redirects and get the project-id.

Problem: If a user has a custom domain and adds that to their environment variables Trigger.dev is not able to use the Supabase Management API.

The issue seems to be trigger is using the URL from the config (expecting {project-id}.supabase.co format).

But if it's a custom domain trigger extracts the subdomain and uses that as the project id.

n/a described below

Reproduction

Add a custom domain in a supabase project

Add the custom domain to the .env

Note how triggers are not created and received a 403 error.

Workaround

The user must use the {project-id}.supabase.co format in their environment.

I do not know if there are other issues with doing this yet but suspect so.

Workaround

The user must use the {project-id}.supabase.co format in their environment.

I do not know if there are other issues with doing this yet but suspect so.

Suggested fix

If the supabase url is not in the {project-id}.supabase.co format, do an nslookup to see where it redirects and get the project-id.