List supabase users instead of hardcoding uuid

[kalilsn]

This fixes login, which was failing because the UUID of our sole supabase auth user didn't match the UUID in the postgres database. I had hardcoded that value in the seed script previously, but the supabase auth user was deleted and recreated (not by the script) which gave it a new UUID.

To fix, instead of looking up the user by hardcoded id, we list all supabase users and just take the first one. This won't work once we have multiple users! But I'm not sure a better way at the moment because supabase doesn't let you look up users by email.

[render]

Your Render PR Server URL is https://core-pr-71-2lkx.onrender.com.

Follow its progress at https://dashboard.render.com/web/srv-cjt0boabgj9c73d43smg.

[gabestein]

If I understand correctly, I think you could query the user by email via prisma, since we're duplicating supabase auth users in the public.auth.

Nm, I see. I think the right way to do this is to setup a trigger that automatically creates the user in public.auth. That's what supabase, etc., recommend, and I'm not sure why we're only doing an update trigger. I'll add this next week.

[isTravis]

A bit of discussion about why we don't have a trigger on user creation is here and under the pages/api/user description bullet in this PR.

[gabestein]

I see. This feels like something we can add to the backlog and try for once the sprint is over. I don’t think it’ll be too tough to replicate the function in sql and we’ll get the benefit of atomicity. But we don’t need it now.

…

On Thu, Sep 7, 2023 at 20:54 Travis ***@***.***> wrote: A bit of discussion about why we don't have a trigger on user creation is here <https://github.com/pubpub/v7/tree/main/core#authentication> and under the pages/api/user description bullet in this PR <#48 (comment)>. — Reply to this email directly, view it on GitHub <#71 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAE4BBRHJR6WUKTKYXDLEWDXZJUEJANCNFSM6AAAAAA4PG7AOA> . You are receiving this because you commented.Message ID: ***@***.***>