Does an API endpoint exist such that I could programmatically add to the db_schema config of PostgREST? Trying to do this locally (for testing) as well as production. I've got supabase deployed in local docker for testing.

Hello @Garett MacGowan! This thread has been automatically created from your message in #843999948717555735 a ``few seconds ago``. Pinging @User so that they see this as well! Want to unsubscribe from this thread? Right-click the thread in Discord (or use the ... menu) and select Leave Thread to unsubscribe from future updates. Want to change the title? Use the

/title

command! We have solved your problem? Click the button below to archive it.

I don't believe I can use

https://api.supabase.io/platform/projects/{my-project-key}/config?app=postgrest

with auth as the bearer token since it will expire. Nothing has jumped out at me from the official/community repos.

Can you say what you trying to accomplish? I think this API setting tells PostgREST what schemas can be accessed:

Garett MacGowan (2022-04-30)

Yeah, I'm trying to programmatically change that setting. Basically, I need to know the local version of the endpoint above, and then I need to know how I can programmatically get the JWT bearer token so I can use the endpoint.

Are you saying that setting is not available in local version of Supabase?

Yeah, I opened a ticket for that design issue. Basically, I'm unsure what the URL for the local version is, and I'm unsure about authorizing the request. I suppose I can just use the service_role secret (obviously just for a backend use)?

I don't use local, so I'm asking again the local studio does not have that setting?

Oh, I see what you're saying. I haven't tried opening the local app.supabase.io. Wasn't even sure if that was included.

There is a local studio version that does all the database stuff of the online dashboard.

Yeah, my use case is that I will be creating multiple schemas so I don't want to have to remember to toggle it manually every time.

You might look into the studio code and see what it does for that setting.

Local studio does not have the settings. I tried hitting the endpoint on the hosted Supabase that I scraped from the dev console when toggling schemas manually. I can't get the service_role key to work as the bearer token. The token I see in the console is unrecognizable. It works fine with the scraped bearer token, but that token expires quickly. I seem to have found a direct approach in https://postgrest.org/en/latest/configuration.html#in-database-configuration. Not sure how I would implement this since the pgrst schema does not appear to be exposed anywhere.

I'm puzzled as even just using another schema with supabase.js (which would be more common than realtime) requires changing that setting. I've not run across any complaints before, not to say I've seen all discussions. (edit: but maybe you did get the dashboard working locally, it is just not sufficient for what you want to do)

Much appreciated. I tried minting the JWT with the role through the link and through a python package and neither worked with the original URL

https://api.supabase.io/platform/projects/{my-project-key}/config?app=postgrest

. 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.

well good luck. I'm going to stop monitoring this thread, so probably should start a new one for anything else.

Ok, thanks for the help.

> Does an API endpoint exist such that I could programmatically add to the db_schema config of PostgREST? @Garett MacGowan This should be handled with care and is not exposed through the UI, but you can use: https://postgrest.org/en/stable/configuration.html#in-database-configuration Through an RPC to programatically add schemas to postgREST. (make sure to include the default schemas in the supabase UI - like storage)

Awesome, that worked. Unfortunately the UI doesn't update to reflect the changes to the config (I assume because its the intra DB config, and Supabase is probably reading from a file, but the intra DB config takes precedence). I can deal with that, though. I'll update my feature request to include this as an alternative.