feat: support region configuration option
#5901
Conversation
|
This pull request adds or modifies JavaScript ( |
|
|
||
| const source = ` | ||
| export default async () => new Response("Hello!") | ||
| export const config = { region: 'mars-west-1' }` |
| 'eu-central-1', | ||
| 'eu-north-1', | ||
| 'eu-south-1', | ||
| 'eu-west-1', |
There was a problem hiding this comment.
does it make sense to include the regions that we don't support in self-serve mode (docs)? The reason we wanted folks to go through Support is to assess whether customers really need these
There was a problem hiding this comment.
Ah, good catch. I copied this list from the UI but didn't realise two of the regions had a boolean set to false. I've removed them in 8546f9c.
There was a problem hiding this comment.
Oops, there's a third one. Fixed in 30be130.
|
|
@eduardoboucas is this still something you'd like to get shipped? |
Yes, just deprioritised. |
Summary
Adds a
regionproperty to the in-source function configuration options.Part of https://linear.app/netlify/issue/RUN-1086/add-region-selection-to-in-source-configuration-options.