Garett MacGowan04/30/2022, 12:00 AM
Needle04/30/2022, 12:00 AM
command! We have solved your problem? Click the button below to archive it.
Garett MacGowan04/30/2022, 12:06 AM
with auth as the bearer token since it will expire. Nothing has jumped out at me from the official/community repos.
garyaustin04/30/2022, 12:14 AM
Needle04/30/2022, 12:14 AM
Garett MacGowan04/30/2022, 12:17 AM
garyaustin04/30/2022, 12:18 AM
Garett MacGowan04/30/2022, 12:27 AM
garyaustin04/30/2022, 12:28 AM
Garett MacGowan04/30/2022, 12:29 AM
garyaustin04/30/2022, 12:30 AM
Garett MacGowan04/30/2022, 12:33 AM
garyaustin04/30/2022, 12:38 AM
Garett MacGowan04/30/2022, 6:06 AM
garyaustin04/30/2022, 6:04 PM
Garett MacGowan04/30/2022, 10:34 PM
. I think the supabase-admin-api is only deployed on the hosted image. I don't see any references to supabase-admin-api in the local docker container. It also isn't included in the architecture map. You can't access the config in the API since everything in the API is routed through Kong. If I try and access the pgrst schema of PostgREST (where I could update db-schema, theoretically) I get the same problem that only the UI can solve, except it can't, since the UI doesn't offer pgrst as a schema to include in the API. Only solution for me is direct manipulation of the config, which is only possible through local, and would take some tinkering. I think my interim solution might be to just run E2E tests on a dev instance of supabase and manually toggle schemas for now.
garyaustin04/30/2022, 10:37 PM
Garett MacGowan04/30/2022, 10:37 PM
Steve05/01/2022, 6:47 AM
Garett MacGowan05/01/2022, 3:56 PM