1
Edge functions: regional invocation with an array of allowed regions
Source: supabase/supabase#34527 · opened by @nurulualp
Currently one region can be selected with x-region for regional invocation. However, I could not confirm if there is re-routing or not if selected region has an outage. I submitted a bug report for this. This might create compliance issues if request re-routes to an unwanted region. Also, even if the feature is working correctly, being able to select only one region might create service interruptions to the user when the selected region is down or might experience latency. If there is an allowed list, it can solve this issue. Proposed request with a new header 'x-allowed-regions' :
curl --request POST ' \
--header 'Authorization: Bearer ANON_KEY' \
--header 'Content-Type: application/json' \
--header 'x-allowed-regions: ["eu-central-1", "eu-west-1", "eu-west-2", "eu-west-3"]' \
--data '{ "name":"Functions" }'
curl --request POST ' \
--header 'Authorization: Bearer ANON_KEY' \
--header 'Content-Type: application/json' \
--header 'x-allowed-regions: ["eu-central-1", "eu-west-1", "eu-west-2", "eu-west-3"]' \
--data '{ "name":"Functions" }'
No pledges yet. Be the first to back this.
Comments
Similar requests
Add CSV Delimiter Configuration Option
5 votes · 0 comments
Dashboard: Link from Edge Functions Invocations to Edge Functions Log with filter on execution ID
1 vote · 0 comments
Enable Syncing of Vault and Edge Function Secrets
1 vote · 0 comments
NestJS Support in Supabase Edge Functions
17 votes · 0 comments
Improving the functionality of Edge Functions
3 votes · 0 comments
No comments yet.