-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Support Edge API Route and Edge Config as kv Store #881
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Thanks! I appreciate the effort. I've been meaning to do this myself. One question: does dropping |
new api using edge runtime need to explictly enable via edge config (`edge_runtime: true`)
In the latest commit I've hidden the new features behide flag so that it won't break existing websites. By default API requests is redirected to function with node runtime that uses ioredis as before, and the new features need to be explictly enabled via Edge Config with |
BTW, although this PR no longer include breaking changes, and the logic of API should be the same, refactoring API with fetch API may introduce unexpected issues. Maybe you can help test it out before merging it if it's convenient for you? |
Noted, thanks for the effort. I'll review this asap ;) |
CDN caching for raw file requests is implemented in cbedcf6. The redirect request is cached for one hour before expire time based on microsoft-graph API document |
Description
@/*
) and config dir (@cfg/*
)Both changes should speed up the response time
Addition
Considering the nature of Edge Config, It's possible to migrate some config like
protectedRoutes
andclientId
so that changing them won't require rebuilding the website