feat: exposing new api keys to functions#4946
feat: exposing new api keys to functions#4946kallebysantos wants to merge 3 commits intosupabase:developfrom
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Central YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
e069a4f to
6c2707d
Compare
6c2707d to
465206c
Compare
Pull Request Test Coverage Report for Build 23016628491Details
💛 - Coveralls |
|
@kallebysantos ping me up when this is ready to merge 👍 |
What kind of change does this PR introduce?
Feature
What is the current behavior?
New api keys (
sb_xxx) are not available inside edge-functions environmentWhat is the new behavior?
This PR exposes the new api keys by creating two new envs:
SUPABASE_PUBLISHABLE_KEYS={"default":"sb_publishable_xxx"}SUPABASE_SECRET_KEYS={"default":"sb_secret_xxx"}Towards AUTH-1040
Prepares CLI to project